-
Default values for optional parameters
- break forwarding in ugly ways,
- pollute interfaces in confusing ways,
- become part of the signature of the method so that it affects subclasses, and
- don't …
-
First of all, thanks so much for making this. It's made my life a lot easier.
Currently, methods in annotations are also inspected and reported if not annotated. Since annotation attributes are inh…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: master version
- OS(Ubuntu or CentOS): MacOS
- CPU/Memory: M1 MA…
-
### Describe the Bug
Reference assembly source code does not include nullability attributes which are required parts of the signatures. For example, these methods failed to include the `[NotNullWhe…
-
Update [nullable-reference-types.md](https://github.com/dotnet/roslyn/blob/features/NullableReferenceTypes/docs/features/nullable-reference-types.md) to use the term "unknown" rather than "oblivious" …
cston updated
3 years ago
-
Originally from https://github.com/mjkoster/ODM-Examples/issues/4:
> From a data modeling policy issue, we should consider establishing a convention that the 0th enumeration is always “Unspecified”…
-
For example, a lot of methods can be turned into extension methods. Nullability is handled strictly be the type system, built-in support for IntelliJ, TCO, inline functions and etc.
It will be a go…
-
For example `DeferredRunnable(StartPolicy)` does not check if its argument is null or not, perhaps assign a default value just like `DeferredCallable` does.
It might be a good idea to state the `nu…
-
-
There are new test failures on [[cfe] Use unwrapping of nullability constructor in upper bound](https://github.com/dart-lang/sdk/commit/1b2c267bb23ff7d6cb5c5cb6c66203cef72b9a65).
The tests
```
fl…