-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Function$
entirely.
#7200
Conversation
f1f3b71
to
79a3876
Compare
fca8ee2
to
01e5837
Compare
tests/syntax_tests/data/parsing/errors/expressions/expected/array.res.txt
Show resolved
Hide resolved
@@ -2,11 +2,11 @@ | |||
|
|||
module V4C = { | |||
@res.jsxComponentProps | |||
type props = {} | |||
type props<'a, 'b> = {a: 'a, b: 'b} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mununki are these changes good or bad?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add test to analysis (so it's compiled and uses rescript-react as a dependency) that these compile.
Tested that the same example did not compile on master, so this is the intended transformation that was somehow lost along the way sometime.
tests/analysis_tests/tests-reanalyze/termination/expected/termination.txt
Outdated
Show resolved
Hide resolved
tests/syntax_tests/data/parsing/errors/expressions/expected/array.res.txt
Show resolved
Hide resolved
tests/syntax_tests/data/parsing/errors/expressions/expected/consecutive.res.txt
Show resolved
Hide resolved
@cknitt we can move to testing phase with this. |
There was a problem hiding this 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: 7d4af4a | Previous: e1b7fb7 | Ratio |
---|---|---|---|
Parse RedBlackTree.res - time/run |
1.3137930666666666 ms |
1.2123143266666667 ms |
1.08 |
Parse Napkinscript.res - time/run |
43.116282813333335 ms |
39.28006235333333 ms |
1.10 |
Parse HeroGraphic.res - time/run |
6.496717546666666 ms |
5.13472718 ms |
1.27 |
This comment was automatically generated by workflow using github-action-benchmark.
@cknitt all the issues are resolved now, did you test this entirely on one project already? |
Yes, did that before, and now just retested with the last commit. Everything builds fine. However, I found that the editor tooling crashes:
|
Ok, that seems to be using the analysis exe that comes with the VS Code plugin for some reason. |
Great, this PR is ready to go then. |
This is already (mostly) done, but not merged yet: rescript-lang/rescript-vscode#1055 |
The arity attribute goes on the `Function$` ast node, not the `Pexp_fun` one.
0c15ebc
to
0196c82
Compare
This could be squash merged, but it would mess up rebasing #7195 |
Change the AST and compiler back-end so that
Function$
is not used anymore to encode function definitions.