-
Notifications
You must be signed in to change notification settings - Fork 0
out
statement
#1259
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 acco 8000 unt related emails.
Already on GitHub? Sign in to your account
Comments
Merged
Merged
lars-reimann
added a commit
that referenced
this issue
Nov 10, 2024
Closes #1259 ### Summary of Changes Add a new kind of statement, the output statement, to inspect results of expressions without creating useless placeholders.
lars-reimann
pushed a commit
that referenced
this issue
Nov 24, 2024
## [0.22.0](v0.21.1...v0.22.0) (2024-11-24) ### Features * categorize API elements ([#1263](#1263)) ([d0d971e](d0d971e)), closes [#1243](#1243) * disable inlay hints for assignee types by default ([#1260](#1260)) ([a651ade](a651ade)) * improve error messages from linker ([#1272](#1272)) ([eddd868](eddd868)), closes [#1268](#1268) * output statement ([#1262](#1262)) ([011ba31](011ba31)), closes [#1259](#1259) * remove schema concept from grammar ([#1273](#1273)) ([1a3bf80](1a3bf80)), closes [#1133](#1133)
🎉 This issue has been resolved in version 0.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
In order to get the output of the operations, users must use code lenses. These are only shown for placeholders, depending on their type.
Because of this, users must create many placeholders in their program that are solely used for output, but never referenced. Still, each placeholder must have a unique name, which either means that users spend time thinking of a proper name, or just quickly give them some garbage name.
Desired solution
Add a new statement
out <expression>
,that is essentially an expression statement that shows code lenses. Determine the names shown in the code lenses based on the results of the function, if
<expression>
is a call. Otherwise, just call it "expression".Keep the current behavior of
_
,Possible alternatives (optional)
Screenshots (optional)
No response
Additional Context (optional)
out
is already a keyword in the language (covariance), so this PR is a non-breaking change.Tasks:
out
is only allowed in pipelineThe text was updated successfully, but these errors were encountered: