Displaying 1 result from an estimated 1 matches for "islazy".
Did you mean:
is_lazy
2017 Oct 14
2
Reducing confusion around isUndefined()
...will be undefined on the final symbol table. The actual predicate for
that is isInCurrentDSO().
In some other cases the intention was to check if we had a definition
already, in which case the code should check also for lazy symbols
too. We don't currently have a predicate for isUndefined() || isLazy().
Some ideas to try to make this less error prone.
* Add a isNotDefined() predicate for isUndefined() ||
isLazy(). Unfortunately the name would be confusing.
* Have Lazy inherit from undefined. Very few places want to check just
for undefined, so they can use kind() directly and isUndefined...