Skip to content

Allow disabling type safety checks for mutable HashMapContexts#165

Open
FruitieX wants to merge 1 commit intoISibboI:mainfrom
FruitieX:rasmus/type-unsafe-context
Open

Allow disabling type safety checks for mutable HashMapContexts#165
FruitieX wants to merge 1 commit intoISibboI:mainfrom
FruitieX:rasmus/type-unsafe-context

Conversation

@FruitieX
Copy link
Copy Markdown

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_functions and associated functions.

I'm creating a program that's responsible for my home-automation systems, and using evalexpr I 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.

@FruitieX FruitieX force-pushed the rasmus/type-unsafe-context branch from 60c589e to 582dd37 Compare January 17, 2024 07:55
@ISibboI ISibboI force-pushed the main branch 6 times, most recently from e4a8571 to 6608b16 Compare October 11, 2024 15:01
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