-
-
Notifications
You must be signed in to change notification settings - Fork 150
T.Writable is not exported #11 #12
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
Conversation
@pirix-gh I hope this PR will suite your standards |
I'm investigating your PR to see if this could be applied to all the types |
TypeDoc is giving me problems generating the docs when using |
Seems like I'll have to add |
Ok, it's not possible to generalize it like I said. But it's now fixed with your changes. Thanks! (v2.1.5) |
Always happy to help! |
Feel free to assign me future issues |
There's going to be a 3.x update with a few breaking changes. Those will improve type soundness and provide computations that have minimum impact on the global performance. It's a sacrifice that is needed. |
When can we expect that version? I will defer my work until then as I use this library extensively now |
I don't know for sure. But I'm giving myself a deadline of 5-6 days from now, going to try to rush it though. I'll keep you updated. But as I said, It will also help to fix types that don't work well on unions, which is a bug. So it's a 2-in-1 update. |
🎁 Pull Request
tst
folder)npm test
Fixes
Fix T.Writable is not exported #11
Why have you made changes?
To fix #11
What changes have you made?
Tuple/_api.d.ts
file.What tests have you updated?
tst/Tuple.ts
Is there any breaking changes?