-
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…
-
```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.
```
-
Currently, NilAway does not track nilability checked via custom boolean returning functions. Hence, this results in false positives, such as in the example shown below.
```
func isValNil(val *int)…
-
Related #14361, #14273
Bug. Nilability. Resizing to a smaller domain when an associated array is of managed *non-nilable* class type will attempt to default-assign `nil` to the disappearing element…
-
I opened and closed two issues today because I forgot to write
```chapel
var b: shared Bar?;
forwarding b!;
```
instead of
```chapel
forwarding var b: shared Bar?;
```
The error messages we…
-
This issue belongs to the following build:
```
go version -m C:\src\go\bin\nilaway.exe
C:\src\go\bin\nilaway.exe: go1.21.3
path go.uber.org/nilaway/cmd/nilaway
mod go.ube…
-
We had faced a nil pointer error in this [line](https://github.com/snapp-incubator/s3-operator/blob/5052540a0ce00b0b06ee8a1fc596a94b5a661d53/internal/controllers/s3userclaim/provisioner.go#L330) of th…
-
We would like to allow the user to declare the return/yield type of a function simply as `owned`. However, the compiler does not allow this currently. Ditto `shared`, `borrowed`, `unmanaged`.
Test:…
-
As a Chapel programmer, I want the ability to utilize constrained generic interfaces because of their value in documenting a library routine's expectations of its arguments, making generic libraries t…
-
The following code reports a false positive.
```
func test(mp map[string][]*int) {
sl := mp["foo"]
slLen := len(sl)
if slLen == 0 {
return
}
_ = sl[0] // FP: error: deep read from param…