Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Feat: Dafny format file.dfy and IDE extension #2399
Feat: Dafny format file.dfy and IDE extension #2399
Changes from all commits
d16d4da
affbc10
0fb6675
1adc50a
3b0c4c5
1417745
84fccd1
d33ea6f
916dab3
bd0451b
3403297
61db34c
a4df959
5d35232
b660509
a8cea01
228eba9
0b6351a
c5716a6
92e9029
c54ea76
c2c0ca2
6492b76
5a45cb2
e2c40ff
0c2684d
62db98f
e557e09
d33ab23
c976656
052a07d
64a2eda
1726661
176fa3f
9b42af0
d79ceb2
42a6053
0a4384c
8ef7192
6569d33
bdcc9a2
5c30819
3d85b10
b671096
0cbc911
33f0774
13b26f0
07cc6d2
0955e4a
76df147
edd87e8
5fcfba7
58d90d0
ae2af6f
1937c81
d8312f4
41c3744
2759d42
4cd5c19
ff9c042
5315ffa
87942c9
61212cf
df29fab
2fb6762
ff4e80a
49bfee2
efaf165
ab5f62d
48d0271
f92cdb7
99a5364
0f27aa5
cdbf7e9
ecefc07
116f030
5b2e1fb
a975d08
23a1ae9
2d52aec
bfcbc07
14bee8b
78e2f0a
75266c1
1170e16
6f9f6f3
ee8cc8e
3be8f79
62078f5
35d07ed
d1962f2
68a5a4d
c5ec51c
8ed8a8b
422f94e
d478cc7
b052f5e
c316fa3
0e9c3d8
70c46aa
f8a1982
4b930ee
ad43802
04bdafc
e934fab
769b841
19761f9
f626961
ee65cd7
218771f
6ed732b
0a9d008
3e83655
b6aa69b
b45b2d8
8ca299d
9680661
7216a04
48ba225
74975e2
fbd4c21
6d2e228
4ae8db3
1048226
12ad952
6b0cdb7
471b385
3bd90ba
b4b2c0c
6b33529
71d8474
f7ca328
8ec6c85
361b4b3
0c2b7d8
1d9e416
aaf64ad
13ec228
9c368b3
f3508b3
b976585
7277eca
a665f05
42ba60d
5cb757b
103b7a0
5398021
b0ad862
28fdb6b
2422cc5
b122333
36a4e56
79db3ec
d8fd6a1
824b8db
1d1dd05
e5e658c
cb85dbe
0b74c16
f409101
a6cbcaf
4c8a787
c1cc399
9895fb0
e547f0c
727377f
e25b508
ef7221d
c7c2111
acc3ecc
2cf6a08
4db837f
0e563a4
9f8e58d
f8f90f8
25bc882
696b76d
8bd23a5
7ddcefe
434b1f3
20e0fa3
63d4040
16b8310
fb0e555
358dae1
a163561
a3c804b
eea16d5
84c4030
d994a6c
9aebcd0
3e109e0
7f27457
a17a442
8c87936
c9ab3d8
94182aa
1f44b32
4f54857
4bad284
e2c0186
6d8c5b8
fa77a2b
db57129
233fdb8
967bec9
e5eceaa
a5d243a
22161f1
9fae867
51daed1
07371a1
f16d10c
60ca207
275cba5
386d956
dba9a0b
f339fad
21700d4
7db7c89
9cb0a60
6aa5dfe
3796627
44d21c2
4bc14c4
3de2525
19fa1de
ee4948a
ea2b6ff
31e7409
517948e
456e137
ca05a7c
647ff7d
67a9fe8
4434213
3e3b5ae
d8065e9
0d8946c
96a878c
54fb307
af7bfdf
a4d1103
bd32a64
aceb1cb
b9d7e97
febccad
1222c06
d3b0f8a
9fe876e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I feel the "two state" nature of our current AST, with its pre and post resolve state, is more complex than it needs to be. I'm hoping that at some point we can remove the
ResolvedExpression
andResolvedStatement
concepts from our AST.How would you feel about cloning the AST after parsing, so you can use that instead of having to define and implement
PreResolveSubExpressions
?Making a clone has a small performance penalty, but I expect us to make post-parsing clones anyways once we start adding caching to our pipeline, so that files which have not been changed but need to be re-resolved because their imports changed, don't have to be parsed again.
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.
+ 1
I would be all in so that
SubExpressions
is a single field instead of two. The problem is, as @cpitclaudel mentioned it, that.SubExpressions
's specification is only specified in the comments to list sub expressions after resolution, not just after parsing. So there would be an inconsistency.Maybe for the scope of another PR?
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.
As discussed elsewhere, we will remove ConcreteChildren and PreResolver by cloning the AST before resolution, but we'll do that in another PR.