Skip to content

CSE: imported rune constants appear to be bound to null #2908

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.

Sign up for GitHub

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

Jump to bottom
Closed
martin-henz opened this issue Apr 8, 2024 · 1 comment
Closed

CSE: imported rune constants appear to be bound to null #2908

martin-henz opened this issue Apr 8, 2024 · 1 comment
Labels
Bug Something isn't working medium

Comments

@martin-henz
Copy link
Member

The environment frames show null for imported constants.

Screenshot 2024-04-08 at 9 33 25 AM

The evaluation works, however, and the evaluation of name occurrences leads to pushing the correct values.

Screenshot 2024-04-08 at 9 36 25 AM
@martin-henz martin-henz added Bug Something isn't working medium labels Apr 8, 2024
@CZX123 CZX123 mentioned this issue Apr 8, 2024
Merged
@martin-henz
Copy link
Member Author

Note: The stepper seems to have solved this problem and could serve as inspiration:

Screenshot 2024-04-08 at 10 53 45 AM

@CZX123 CZX123 mentioned this issue Apr 9, 2024
Merged
@martin-henz martin-henz changed the title CSE: imported constants appear to be bound to null CSE: imported rune constants appear to be bound to string; formating issue Apr 10, 2024
@martin-henz martin-henz changed the title CSE: imported rune constants appear to be bound to string; formating issue CSE: imported rune constants appear to be bound to null Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something isn't working medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martin-henz