Jonas Kello

Yes, I did have a quick look at @rluiten repos but as I understand it that is a re-implementation in typescript rather than just types for the existing packages. I've...

Thanks for taking the time to contemplate this! Just to clarify there are three ways we could add types: 1. Put a `index.d.ts` file in the root of the repo...

So I did a PR to support this discussion in #32.

@pandorasNox Opaque types are definitely a good idea. I suggested it in the typescript repo [#15408](https://github.com/Microsoft/TypeScript/issues/15408) and [#15465](https://github.com/Microsoft/TypeScript/issues/15465) however it seems typescript will not implement them although flow has since...

@mindplay-dk Good point That works because typescripts uses structural typing instead of nominal typing. We can take advantage of structural typing to have less type-coupling.

@mindplay-dk I did a similar thing. I wrote something similar to raj in typescript and since then I have re-written that library several times as I needed to add more...

Yes, I agree we should make the order of type params consistent if this would ever get merged. Regarding `TView`, having done a lot of C# that is what I'm...

We've put the current work in progress in the [eslint-plugin-ts-immutable](https://github.com/jonaskello/eslint-plugin-ts-immutable) repo/package. This plugin has three rules, no-let, no-this, and no-mutation. The `eslint-plugin-ts-immutable` plugin covers these rules and add more rules....

I initially thought this was a good idea too. But maybe a better idea is to implement #4 and then all uses of Object.assign() would be banned (as it does...

@ljharb: Actually I think object spread operator is at [stage 2](https://github.com/sebmarkbage/ecmascript-rest-spread#status-of-this-proposal).