-
## The Problem
The `tapioca` compiler for ActiveRecord models makes most columns nilable, ignoring database constraints.
This is correct on paper, because when you call `Model.new` none of those w…
-
Nilability ergonomics / convenience features have been proposed in #12614 and forked off into #16931. The first of them is the topic of #13639, already implemented.
This issue requests the second c…
-
With the recent nilability changes in the language, the TOML package has received various organic updates to keep it working and passing testing. However, these updates have led to an inconsistency in…
-
When creating a variable of a class/record type that has a field of a generic type, the compiler needs to check that the instantiated field's type has concrete nilability and memory management. Otherw…
-
Currently we cannot pass ``nil`` to a nilable, un/managed, but otherwise generic formal. This seems reasonable seeing as ``nil`` can't contain the relevant information to instantiate the generic forma…
-
Currently, when calling a method on a nilable class, the error message we get is quite long and quite general. E.g., for this test [[ATO]](https://ato.pxeger.com/run?1=m70sOSOxIDVnwYKlpSVpuhY3o5NzEou…
-
Regarding nilability, should the compiler emit a warning that the nil-check is unnecessary? Maybe there's a reason I'm missing that the nil could e.g., be propagated somewhere despite the non-nilable …
-
Usability problem statement for nilability. The actual problem is with localized error handling of exceptions that becomes exacerbated with nilability.
Possibly a non-issue, though it's annoying to…
-
Currently this code:
```chpl
class Block {
proc init(targetLocales: [] locale) {...}
}
var targetLocales: [....] locale?;
populate targetLocales;
... new Block(targetLocales!) ...
```
d…
-
```chpl
proc p() : object? {
return nil;
}
writeln(p());
```
**Output**
```
segfault.chpl:5: internal error: seg fault [util/misc.cpp:672]
Note: This source location is a guess.
```