Allow disabling type safety checks for mutable HashMapContexts #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FruitieX
force-pushed
the
rasmus/type-unsafe-context
branch
from
60c589e to
582dd37
Compare
ISibboI
force-pushed
the
main
branch
6 times, most recently
from
e4a8571 to
6608b16
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it possible to disable the type safety check in
HashMapContext::set_value().I tried to stay consistent with the naming of
without_builtin_functionsand associated functions.I'm creating a program that's responsible for my home-automation systems, and using
evalexprI can make some simple scriptable rules and actions for it. This worked fine until I ran into a problem where I cannot assign another value to a variable if it already contains an empty value.