-
In the current implementation of cppfront (065a993), the following code compiles and runs:
```cpp
i : int = 123;
std::cout
-
I noticed while looking at TodoMVC that the following isn't fully typesafe,
```typescript
return accumCombine(
[
[prependItemS, (item, list) => [item].concat(list)],
[
…
-
currently all of the interfaces are implemented as traits on Id. This means there's no type safety between objects. We should probably use something like the foreign_obj_type! macro from https://githu…
-
We're doing a quick POC and looking at using this library. One thing that I'd love to see is the ability to enforce or at least make consistent the concept of fact types. Something along the lines of:…
-
### Reason/Context
One of the challenges I face when using Glee is the uncertainty of the values in message payloads. Seeing the "any" type in Typescript can also be a bit intimidating. 😆
However…
-
LazyModel is type-safe regarding the model object (last getter), but not regarding the root object (what we pass to the from() method). Thus, the bind() method receives Object, and it is not possible …
-
re github.com/gogo/protobuf/protoc-gen-gogo/generator/generator.go
Line 1481 is `func generateEnum`, which produces two tables, X_name and X_value, both of which are a `map`. They both use `int32`,…
-
There is a unused generic in the https://github.com/aralroca/next-translate/blob/master/docs/type-safety.md.
``.
-
It would be helpful to have type safety between deviceId and devicePtr since it is very easy to pass in the wrong one
-
Incorrect quick for Type safety warning:
![issue_1](https://user-images.githubusercontent.com/5179063/38723512-e71405a2-3f33-11e8-8e4f-ef2ec975a23f.PNG)
Fixed the type, warning gone:
![issue_…