objectionary / objectionary/reducing-programs-to-objects
Nullptr - what analogue should be proposed in translators
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 15
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by resolving the proposed EO representation for null pointers and the cross-type equality behavior described in the issue; done means the null-pointer design and (nullptr == nullptr) semantics are decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100