Allow nullable primitive types, so they can be used as return type
Open
@IsakNaslundBh is already working on this.
Since Jul 3, 2020.
Assessment
This issue has not been assessed yet.
Description
type:feature
Description:
As discussed in the Error Management Workshop (notes here).
Nullable primitive types would allow for an additional mechanism for better error handling. Instead of returning a boolean or an empty data in case a method fails, we could return a null.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from BHoM/admin
-
type:question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Refactoring and documentation based on "Universal" common interfacesMay be free again @al-fisher claimed this 1897 days ago, and no pull request is open. Opentype:compliance
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
type:feature type:question
-
type:compliance