Bruce Pascoe
Bruce Pascoe
Yeah, I see what you mean. My other idea was `->` but that might get confused for an arrow function.
Ideally I'd also want an option to build in `~/Sphere Games`, since that's where minisphere (as of 1.5.3) looks for games when `GetGameList()` is called.
I definitely think we should switch to a JSON-based project system, but that's something for 2.0 I'd say. For now we should stick to the INI format as that's what's...
Sphere Studio now has a dependency on Json.NET because it's required for source map support. Now would be a good time to implement this, I think.
It might be worthwhile to implement this through the preset system so that you can associate files with different plugins. The current preset could even be stored in the .ssuser...
`never` is the bottom type and is intentionally assignable to all other types. This is because the type is an empty set and has no inhabitants - by definition you...
To clarify since this is a common point of confusion: `{ work: never }` *doesn't* mean an object that never has a `work` property. It means an object that *always*...
The problem with the example, and why it’s not an error as written, is because `JSON.parse` returns `any`. That’s a separate issue; the part where `{ work: never }` is...
> I fail to see, that assigning an impossible type to a possible type can be a correct, type safe assignment. It’s a bit weird, but the mathematical explanation is...
> I think you missed the implicit cast due to the type annotation in the function header 😉 That's not a cast, it's just a normal return type annotation. If...