Skip to content
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

Esl2 #253

Merged
merged 3 commits into from
Nov 30, 2024
Merged

Esl2 #253

merged 3 commits into from
Nov 30, 2024

Conversation

divarvel
Copy link
Collaborator

@divarvel divarvel commented Nov 30, 2024

see #252

#252 was stuck processing commits and wasn’t getting updated.

according to the grammar, `{}` could either mean *empty set* or *empty map*. Due to how the parser was written, it was always an empty set, and there was no way to have an empty map literal.

This is an issue because empty maps would still be displayed as `{}`, and maps have a different api than sets, resulting in evaluation errors.

This commit introduces `{,}` as the empty set literal, while `{}` is the empty map. The goal here is to be consistent with JSON, the reason why we chose the current syntax for arrays and maps.
Copy link

codspeed-hq bot commented Nov 30, 2024

CodSpeed Performance Report

Merging #253 will not alter performance

Comparing esl2 (cd5d154) with v5 (fc0d069)

Summary

✅ 12 untouched benchmarks

@divarvel
Copy link
Collaborator Author

#252 has been approved, coverage (measured locally) is fine. The coverage failure in the CI branch has been introduced in a previous PR

@divarvel divarvel merged commit 0dab828 into v5 Nov 30, 2024
7 of 9 checks passed
@divarvel divarvel deleted the esl2 branch November 30, 2024 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant