Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with typescript
Search options not deleted
user 93229
Programming language created by Microsoft. Open source, and compiles to JavaScript.
9
votes
1
answer
7k
views
Is there a convention for the Optional/Maybe monad in typescript?
In typescript this can be represented like this:
function f(): number | undefined {}
A more elaborate way would be to build a maybe type and use that for the typing:
type Maybe<T> = T | undefined; … function f(): Maybe<number> {}
To check the type of the returned value we could use an if:
const x = f();
if (x === undefined) { } else {}
Is there a conventional way to express the optional type in typescript …
- 373