Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Pluggable, 3rd-party Type Systems #2944

Closed
jednano opened this issue Apr 28, 2015 · 1 comment
Closed

Support Pluggable, 3rd-party Type Systems #2944

jednano opened this issue Apr 28, 2015 · 1 comment
Labels
Declined The issue was declined as something which matches the TypeScript vision Suggestion An idea for TypeScript Too Complex An issue which adding support for may be too complex for the value it adds

Comments

@jednano
Copy link
Contributor

jednano commented Apr 28, 2015

There's a library written by @gcanti called tcomb-ats, which is a 3rd-party assertion library for AtScript. Now that AtScript has been replaced with TypeScript, does that change the TypeScript Design Non-Goals in any way? Would support for 3rd-party assertion libraries like tcomb-ats be possible?

If configured the same way, it would go in the tsconfig.json file as such:

{
  "typeAssertionModule": "path/to/tcomb-ts"
}
@danquirk
Copy link
Member

As far as I can tell this is basically asking for a pluggable type system, which essentially no languages do (well). This doesn't look like an assertion library (in the sense of common uses of the term like chai, should, etc), it looks like an entirely new set of primitive types and assignability rules. This isn't something we'd support.

@danquirk danquirk added Suggestion An idea for TypeScript Declined The issue was declined as something which matches the TypeScript vision Too Complex An issue which adding support for may be too complex for the value it adds labels Apr 28, 2015
@jednano jednano changed the title Support 3rd-party Assertion Libraries Support Pluggable, 3rd-party Type Systems Apr 28, 2015
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Declined The issue was declined as something which matches the TypeScript vision Suggestion An idea for TypeScript Too Complex An issue which adding support for may be too complex for the value it adds
Projects
None yet
Development

No branches or pull requests

2 participants