You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, this may or may not be intended behaviour.
I'm writing a package with a new AbstractDict type, which is lazily validated. That means its possible to construct an invalid instance (which may be checked with isvalid). Encountering an invalid value when iterating the dict, or accessing an invalid key will throw an exception.
Problem is, the REPL will access the dictionary while giving autocomplete suggestions (see below)
Is this a problem? Maybe it's fair to assume iterating an AbstractDict never errors.
So, this may or may not be intended behaviour.
I'm writing a package with a new
AbstractDict
type, which is lazily validated. That means its possible to construct an invalid instance (which may be checked withisvalid
). Encountering an invalid value when iterating the dict, or accessing an invalid key will throw an exception.Problem is, the REPL will access the dictionary while giving autocomplete suggestions (see below)
Is this a problem? Maybe it's fair to assume iterating an
AbstractDict
never errors.The text was updated successfully, but these errors were encountered: