4 ms·
Hey I've been enjoying working with TypeScript lately, but when is this bug gonna be fixed: https://github.com/Microsoft/TypeScript/issues/11375 https://github.
by camgunz 8y ago
Hey I've been enjoying working with TypeScript lately, but when is this bug gonna be fixed: https://github.com/Microsoft/TypeScript/issues/11375 https://github.com/Microsoft/TypeScript/issues/11375.
You basically can't implement iterators while using `strictNullChecks`, and it's been broken since at least October 2016 (!)
Every time I go to use TS for a personal project I check to see if this is fixed, and for almost two years the answer is no. I am dying here. Should I not be implementing iterators? Does no one use `strictNullChecks`?
- avtar 8y ago> but when is this bug gonna be fixed: https://github.com/Microsoft/TypeScript/issues/11375 https://github.com/Microsoft/TypeScript/issues/11375 Looks like whenever 3.0 is released.
- camgunz 8y agoThey keep bumping the release marker
- smt88 8y agoIsn't there something like @ts-ignore that lets you disable the type checker on a line-by-line basis?
- tlarkworthy 8y agoYes but it doesn't apply to certain errors unfortunately
- camgunz 8y agoI don't want to ignore every iterator I build. I want it all to be null safe.
- nitinreddy88 8y agoI am assuming you are developer of Js/TS, and being open source your contribution to fix would be welcomed. We expect contributions from everyone thats the motive behind OpenSource And not just being transparent of code
- maxilulu 8y agoHe might be just a consumer not a compiler expert.
- qop 8y agoI have seen the remark you're replying to hundreds of times throughout my career. I've seen probably thousands of complaints about out-of-date exploits or bad kits or including new injections and so on... This isn't infosec, but it IS still FOSS. I've always considered the reminder that open source loves contributions to be a gentle reminder that: * Most FOSS isn't sponsored. * Most FOSS developers/maintainers aren't treated with much courtesy when things go wrong. "you broke my build!" etc. * Without FOSS, a vibrant, interesting world would not exist within our computers, and even though its easy to forget, that world requires a rather significant amount of work for it to turn. Ofc not everyone is a compiler expert. But everybody can help, and certainly everybody can TRY to help. Framing an issue like this with "hey, I'm not a compiler expert but there's this bug and I would love for it to be fixed, I wouldn't even know where to start... It's an older bug, what's the plan?" is much more courteous of the maintainers than "this shit is broke why don't u fix it?!" I'm exaggerating just to illustrate the spectrum. Better and worse examples can be found all across the fossverse. Hell in just the Linux kernel alone there's a whole village of different personalities. My point to all this: it's a very common remark, goes back ages, and I think it's a fantastic denominator to remind people the logistics of foss and human beings. Sorry to hijack your comment!
- Rapzid 8y ago> We expect contributions from everyone thats the motive behind OpenSource And not just being transparent of code This is not a very common remark however.
- camgunz 8y agoHey FWIW I'm aware I'm more or less trying to hijack a release thread with my gripe. I don't think this should be standard practice for FOSS. In my defense though, I waited for years on this bug, I like TypeScript, I want to use it and evangelize it, and this (pretty fundamental) bug has languished meanwhile we got... module types? I'm pretty sure 99.9999% of devs will never use those. I bet they use iterators though. Also I already have a job, and TypeScript is a Microsoft product with many Microsoft engineers working on it every day. Let's not portray it as entirely the altruism of some saintly engineers donating their time. We're not talking about OpenBSD here.