You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: we do have a range positions build, but that doesn't actually run tests with -Yrange-pos, only the distribution itself is compiled with that option.
In general, we don't expect all tests to work under both offset/range positions.
But, a few of the failing cases, such as that above, do indicate bugs.
What is the impact of such bugs?
Currently, they will crash a) the presentation compiler, and b) the build compiler with -Yrangepos set.
The first problem can be avoided altogether by our plan to return macro applications (attributed with the types of the macro expansion) in the presentation compiler.
For the second, we could try to find and fix problems, like this one. But, we might also consider demoting range positition validation crashes to warnings outside of the pres compiler.
Who uses range positions other than the IDE? I've seen some interest from macro authors themselves, who would like to get access to precise source code for macro argument trees.
The text was updated successfully, but these errors were encountered:
Some macro tests fail under
SCALAC_OPTS=-Yrange-pos
Example:
test/files/pos/annotated-original
Note: we do have a range positions build, but that doesn't actually run tests with -Yrange-pos, only the distribution itself is compiled with that option.
In general, we don't expect all tests to work under both offset/range positions.
But, a few of the failing cases, such as that above, do indicate bugs.
What is the impact of such bugs?
Currently, they will crash a) the presentation compiler, and b) the build compiler with -Yrangepos set.
The first problem can be avoided altogether by our plan to return macro applications (attributed with the types of the macro expansion) in the presentation compiler.
For the second, we could try to find and fix problems, like this one. But, we might also consider demoting range positition validation crashes to warnings outside of the pres compiler.
Who uses range positions other than the IDE? I've seen some interest from macro authors themselves, who would like to get access to precise source code for macro argument trees.
The text was updated successfully, but these errors were encountered: