-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Design Meeting Notes, 9/28/2018 #27486
Comments
@RyanCavanaugh Are these design meeting open (or recorded)? |
@shobhitg nope. I don't think a recording is something we could do for a variety of reasons, but I think some other forum to elaborate more on certain decisions would be interesting |
I have two assume two of the "reasons" are:
I can understand that, but it would be really cool if the TS team could occasionally do a live stream where community has chatroom to converse with TS team. Or even just a podcast type thing. It certainly wouldn't be ever week, but maybe 3-4 times a year like for an hour? Just discuss what you're working on, ask for some feedback/answer some questions. Then talk about upcoming plans. Ask the chat what it thinks should be higher priority,etc. I think that because community attendance to a live event poses a "higher bar to entry" compared to posting an issue on GH, that only community members who are truly interested and likely have actual understanding of the topics being discussed would make the commitment to attend. I think there's the potential for some high-level discourse to occur. |
interface
keyword being stomped by TSconst
initializers and parameter values closer to the non-widening areafoo<T>(x: T): T
do with e.g.{ kind: "bar"}
? Return{ kind: "bar" }
or{ kind: string }
? Arguable both wayskonst
extends
path using node_modules resolution logic #18865 Use node module resolution for tsconfig extends filesThe text was updated successfully, but these errors were encountered: