v1.0 Release Checklist

[getify]

• [x] Narrower number type inference #17 (requires #6 too)
• [x] Enforce bool check on if, while, and do..while #7
• [ ] Persistent object/array type shapes #18
• [x] Arrays-of-type syntax (incl multi-dimensional and tuples> #39
• [x] Checker validates tagged-type simple literals #34
• [ ] Compiler: basic transforms #19
• [ ] Specific type exceptions #20
• [ ] Basic configuration #21
• [ ] Fix architecture of check(..) method #22
• [x] Basic checker tests #23
• [x] IIFE as call-expression #33

[dgutson]

@getify any update on this?

[getify]

Unfortunately, no. I didn't really get the uptake in interest I was hoping and trying to evangelize for, so this project has just been indefinitely on the shelf. It's far too ambitious for me to have done myself.

My thoughts around type annotation have moved over to the design of a new programming language, which is where my active efforts are currently focused.

This project is not necessarily permanently shuttered, but I don't see it coming out of hibernation unless I found some financial backing and a group of interested contributors to help me.

[dgutson]

Would you do the last effort and finish the last 5 tasks to do the release honoring all your previous effort? I personally find this project more useful and applicable than a brand new language for the every-day working layman.

Finding contributors would be easier for a baselined 1.0. Also, maybe you could do a university tech talk about this project (I can contact you later).

[getify]

Would you do the last effort and finish the last 5 tasks

At the time I was actively working on this, I felt like I was about 60% of the way to a 1.0 release, and that I probably had about 4 months FT effort to complete it. I would love to have 4 months to dedicate to this, but I cannot afford that. And working on it a few hours at a time would take a year or two, which I just don't have the long-term interest in enough to sustain.

If I found funding to pay for 4 months of my effort, I would probably do it. But I spent a fair bit of effort shopping this around to some companies and folks I knew, and most of them felt it was not a worthy investment because TypeScript was so inevitable as the "winner" in this space.

[dgutson]

Are you familiar with Instagram's MonkeyType? Could TypL be the basis for an equivalent for javascript?

[getify]

Never heard of it, but I just took a quick glance at the README.

One of the modes/tools I had planned for TypL was in fact to be able to gather runtime types (from test suite and/or even staging/production code) and export that information as TypL annotations (diffs that could be applied back to code).

That would definitely have been post-1.0, but yes, I think it's a great idea and I definitely had hoped to build something like that. :)