Skip to content

Conversation

@dawedawe
Copy link
Contributor

@dawedawe dawedawe commented Jul 18, 2023

Combined work with @nojaf

This adds trivia information to SynConst.Measure to help editor tooling dealing with these.

@auduchinok
Copy link
Member

Could you please also capture ranges of optional things, like SynMeasure.One, so we could distinguish parsed and synthetic measures?

@dawedawe
Copy link
Contributor Author

Could you please also capture ranges of optional things, like SynMeasure.One, so we could distinguish parsed and synthetic measures?

Yes, I'll add a range to SynMeasure.One. As far as I can see, that's the only one missing.

@nojaf
Copy link
Contributor

nojaf commented Jul 18, 2023

The interesting use-case for SynMeasure.One would be something like let a = 42< 0_1 / m>.
If we have the range, we can restore the original notation of 1.

 - add tests
 - update baselines
@dawedawe dawedawe marked this pull request as ready for review July 18, 2023 15:19
@dawedawe dawedawe requested a review from a team as a code owner July 18, 2023 15:19
dawedawe added 2 commits July 18, 2023 18:58
- add test
- update surface baselines
@dawedawe
Copy link
Contributor Author

To me, this seems to be okay now. @auduchinok, how about you?

Copy link
Member

@auduchinok auduchinok left a comment

Choose a reason for hiding this comment

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

Just one comment from my side, otherwise it seems good to go in. Thanks @dawedawe!

@psfinaki psfinaki enabled auto-merge (squash) July 21, 2023 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

5 participants