Skip to content

Conversation

cristianoc
Copy link
Collaborator

The check was not firing for module M: ModTyp as it was looking for attributes in the wrong place.

@cristianoc cristianoc force-pushed the async-context-module branch 3 times, most recently from ed00b7e to 3005e77 Compare February 1, 2025 12:58
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Syntax Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.05.

Benchmark suite Current: eccff4f Previous: e1b7fb7 Ratio
Parse RedBlackTree.res - time/run 1.3688083599999998 ms 1.2123143266666667 ms 1.13
Parse Napkinscript.res - time/run 42.731040799999995 ms 39.28006235333333 ms 1.09
Parse HeroGraphic.res - time/run 5.766649673333333 ms 5.13472718 ms 1.12

This comment was automatically generated by workflow using github-action-benchmark.

@cristianoc cristianoc requested review from cknitt and zth February 1, 2025 13:01
The check was not firing for `module M: ModTyp` as it was looking for attributes in the wrong place.
The module constraint can originate from `module M: MT = await N` or from `module M = await (N: MT)` and the attributes go to the module id in the first case, but on the constraint in the second.
@cristianoc cristianoc force-pushed the async-context-module branch from f41106f to eccff4f Compare February 2, 2025 10:23
@cristianoc cristianoc merged commit 9de8f34 into master Feb 2, 2025
20 checks passed
@cristianoc cristianoc deleted the async-context-module branch February 2, 2025 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants