Don't throw exceptions in specific HLIL APIs #6020
Labels
Component: API
Issue needs changes to the API
Effort: Low
Issue should take < 1 week
Impact: Low
Issue is a papercut or has a good, supported workaround
Type: Enhancement
Issue is a small enhancement to existing functionality
Milestone
What is the feature you'd like to have?
From an Enterprise user:
Is your feature request related to a problem?
Exceptions don’t play nice with
map()
andfilter()
, butNone
does.Are any alternative solutions acceptable?
I'm not actually sure we should make it not throw an
Exception
. An alternative way we could solve this is by having e.g. aReferenceSource.hlil_if_available
that, under-the-hood, callsFunction.llil_if_available
, which (I believe) does what this user wants.The text was updated successfully, but these errors were encountered: