Timeline for Is it possible to make nonnull become part of C++ type system?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 29, 2019 at 8:45 | comment | added | Aykhan Hagverdili |
@amon you can't store references in a container. You could use std::reference_wrapper though.
|
|
| Jan 7, 2017 at 14:12 | comment | added | gnasher729 | "Billion dollar mistake" is very much exaggerated. It wasn't a mistake in the first place - because nobody had thought of any alternatives when the "mistake" was supposedly made. | |
| Jan 6, 2017 at 18:30 | comment | added | CodesInChaos |
@tofro And that good reason is? I can't think of any advantages null has over a proper option type.
|
|
| Jan 6, 2017 at 15:02 | history | edited | Nicol Bolas | CC BY-SA 3.0 |
added 22 characters in body
|
| Jan 6, 2017 at 15:00 | comment | added | Nicol Bolas | This question would be handled better on the ISO-C++ proposal forum. Q&A is not an effective means for tempering a proposal. | |
| Jan 6, 2017 at 15:00 | answer | added | Nicol Bolas | timeline score: 2 | |
| Jan 6, 2017 at 12:10 | comment | added | tofro | The question would be "is there a good reason for a NULL-safe type system?" - NULL is there for a good reason. | |
| Jan 6, 2017 at 8:00 | comment | added | amon |
References already are non null pointers, with the restriction that you may not reassign them. Most of your suggested behaviours can be implemented with a nonnull<T*> wrapper, no language changes required.
|
|
| Jan 6, 2017 at 7:40 | comment | added | Brandin | Did you look at not_null in the gsl library? Here is one article about it: visualstudiomagazine.com/articles/2016/06/01/… | |
| Jan 6, 2017 at 7:08 | history | asked | Michael Tsang | CC BY-SA 3.0 |