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
Null pointers are such a thing, that we don't tolerate (as is in README mentioned). But when we are trying to translate languages, that have such objects as null, nullptr in EOlang, we face an expected problem. We don't have such an objects in eo.
As I think, the easiest way to make such an analogue is to decorate (int) 0 object with overriden attribute as-hash, that returns -1. But it is not the best idea of the nullptr objects implementation. So, if anyone has any ideas, of how can we recreate nullptrs in EO, please leave some comments here.
Another problem for now is what should return statement (nullptr == nullptr) in cases when they point to different types or not.
The text was updated successfully, but these errors were encountered:
Null pointers are such a thing, that we don't tolerate (as is in README mentioned). But when we are trying to translate languages, that have such objects as null, nullptr in EOlang, we face an expected problem. We don't have such an objects in eo.
As I think, the easiest way to make such an analogue is to decorate (int) 0 object with overriden attribute as-hash, that returns -1. But it is not the best idea of the nullptr objects implementation. So, if anyone has any ideas, of how can we recreate nullptrs in EO, please leave some comments here.
Another problem for now is what should return statement (nullptr == nullptr) in cases when they point to different types or not.
The text was updated successfully, but these errors were encountered: