tc39/proposal-do-expressions issues and pull requests

#78 - Add documentation why a new keyword is necessary.

Issue - State: closed - Opened by jguddas over 1 year ago - 3 comments

#77 - How should this proposal work with pattern matching?

Issue - State: open - Opened by theScottyJam over 1 year ago - 12 comments

#76 - idea: `do *` generators

Issue - State: open - Opened by jedwards1211 over 2 years ago - 2 comments

#75 - Completion value is complex 10 times harder when `break` is involved

Issue - State: open - Opened by Jack-Works over 3 years ago - 17 comments

#74 - Do Expression with Alternative Syntax - Immediately Executed Arrow Functions

Issue - State: open - Opened by EdSaleh over 3 years ago - 33 comments

#73 - Return in function parameter initializer

Issue - State: closed - Opened by Jack-Works over 3 years ago - 6 comments

#72 - Implicit return is bad

Issue - State: open - Opened by 2A5F over 3 years ago - 80 comments

#71 - Alternative proposal: Expression block

Issue - State: open - Opened by Jack-Works over 3 years ago - 43 comments

#70 - Invert the early error condition

Issue - State: open - Opened by lightmare over 3 years ago

#69 - Create expression-oriented control structures instead

Issue - State: closed - Opened by theScottyJam over 3 years ago - 3 comments

#68 - EndsInIterationOrBareIfOrDeclaration missing case: Block with statements

Issue - State: closed - Opened by Jack-Works over 3 years ago - 3 comments

#67 - What would a do statement return?

Issue - State: closed - Opened by Explosion-Scratch almost 4 years ago - 4 comments

#66 - Async identifier/keyword reference inside class static block

Issue - State: closed - Opened by Kingwl almost 4 years ago - 1 comment

#65 - What will happen when control flow changes when a variable is init?

Issue - State: closed - Opened by Jack-Works almost 4 years ago - 3 comments

#64 - Add a badge for specifying current stage

Pull Request - State: closed - Opened by aleen42 almost 4 years ago - 1 comment

#63 - Down level compile memo (tooling)

Issue - State: closed - Opened by Jack-Works almost 4 years ago - 35 comments

#62 - Clarify question: Is it possible to use return in an arrow function with a expression body?

Issue - State: closed - Opened by Jack-Works almost 4 years ago - 2 comments

#61 - isLast

Issue - State: open - Opened by waldemarhorwat almost 4 years ago - 4 comments

#60 - forbid if-without-else as last statement

Pull Request - State: closed - Opened by bakkot almost 4 years ago - 1 comment

#59 - allow return, break, and continue

Pull Request - State: closed - Opened by bakkot almost 4 years ago - 1 comment

#58 - Use-case: lazy expressions?

Issue - State: closed - Opened by getify about 4 years ago - 8 comments

#57 - Isn't this just an immediately invoked function?

Issue - State: closed - Opened by dustbort about 4 years ago - 25 comments

#56 - do expressions can introduce strict mode

Issue - State: open - Opened by bakkot about 4 years ago - 7 comments

#55 - How to return literals?

Issue - State: open - Opened by bakkot about 4 years ago - 36 comments

#54 - Update readme / spec text to match version presented in 2020/2021

Pull Request - State: closed - Opened by bakkot about 4 years ago

#53 - `do { }` vs `do { } while ();` confusion

Issue - State: open - Opened by davethegr8 about 4 years ago - 41 comments

#52 - Cover grammar due to `do { } while`?

Issue - State: closed - Opened by syg over 4 years ago - 8 comments

#51 - Error building spec.emu

Issue - State: closed - Opened by tom-sherman over 4 years ago - 3 comments

#50 - Cannot allow `yield` and meaningfully prohibit `return`

Issue - State: open - Opened by erights over 4 years ago - 11 comments

#49 - Write more detailed explainer and spec text for Stage 2

Issue - State: closed - Opened by littledan over 4 years ago - 1 comment

#48 - Spec needs to handle empty completion values

Issue - State: closed - Opened by bakkot over 4 years ago - 2 comments

#47 - Nesting do(s) for nested control flow, is this necessary, is there a better way?

Issue - State: closed - Opened by hodonsky over 4 years ago - 8 comments

#46 - Major strengths over IIFE's?

Issue - State: open - Opened by brennongs about 5 years ago - 18 comments

#45 - Focus on `const` bindings

Issue - State: open - Opened by mcgwiz over 5 years ago

#44 - Why not support `switch` statements?

Issue - State: closed - Opened by wangzongxu over 5 years ago - 1 comment

#43 - "use expressions" directive

Issue - State: open - Opened by pvider almost 6 years ago - 8 comments

#42 - Can do expression be lazy evaluation?

Issue - State: closed - Opened by zheeeng almost 6 years ago - 3 comments

#41 - Explicit return from normal statements

Issue - State: open - Opened by hagabaka almost 6 years ago - 1 comment

#41 - Explicit return from normal statements

Issue - State: open - Opened by hagabaka almost 6 years ago - 1 comment

#40 - Do expression as a candidate for evaluating tools

Issue - State: open - Opened by codehag almost 6 years ago - 1 comment

#40 - Do expression as a candidate for evaluating tools

Issue - State: open - Opened by codehag almost 6 years ago - 1 comment

#39 - Why not just let statements return value?

Issue - State: open - Opened by kkshinkai almost 6 years ago - 48 comments

#38 - do as computation-expression to solve "async" do and "generator" do

Issue - State: open - Opened by mattiamanzati about 6 years ago - 10 comments

#37 - do expression, generator function and for loop

Issue - State: closed - Opened by xialvjun about 6 years ago - 6 comments

#36 - `DO` should eliminate all statements, convert all statements to expressions

Issue - State: open - Opened by kghost about 6 years ago

#35 - Slightly better first example

Pull Request - State: open - Opened by elibarzilay over 6 years ago

#34 - Do-Expressions vs IIFEs: A Comparison

Issue - State: open - Opened by JHawkley over 6 years ago - 26 comments

#33 - Violating TCP?

Issue - State: closed - Opened by JHawkley over 6 years ago - 15 comments

#32 - Best syntax is {> .....}

Issue - State: open - Opened by pvider over 6 years ago - 19 comments

#31 - context free grammar

Issue - State: closed - Opened by majg0 over 6 years ago - 6 comments

#30 - Early return

Issue - State: open - Opened by qm3ster over 6 years ago - 20 comments

#29 - Is this a syntax sugar for iife?

Issue - State: closed - Opened by lxe over 6 years ago - 2 comments

#28 - About expressions in the header of a block

Issue - State: open - Opened by sffc over 6 years ago - 10 comments

#27 - Tooling implementation status

Issue - State: open - Opened by vjpr over 6 years ago - 1 comment

#26 - Beautify and better examples

Pull Request - State: closed - Opened by andria-dev almost 7 years ago - 12 comments

#25 - Extending ParenthesizedExpression to allow Statement

Issue - State: open - Opened by rbuckton about 7 years ago - 14 comments

#24 - Clarify interaction between do-expressions and break

Issue - State: open - Opened by jorendorff about 7 years ago - 18 comments

#23 - Typo in readme

Issue - State: closed - Opened by jorendorff about 7 years ago - 1 comment

#22 - Rules for nested do-expressions

Issue - State: open - Opened by jorendorff about 7 years ago - 11 comments

#21 - This requires JS programmers to learn a bunch of trivia

Issue - State: open - Opened by jorendorff about 7 years ago - 34 comments

#20 - Use explicit `return`

Issue - State: closed - Opened by kylejlin about 7 years ago - 15 comments

#19 - Spec in the works?

Issue - State: closed - Opened by pitaj about 7 years ago - 1 comment

#18 - What is the expected behaviour in sub expressions of a do expression?

Issue - State: open - Opened by kasperpeulen about 7 years ago - 11 comments

#17 - Shorthand function `do` syntax

Issue - State: closed - Opened by pitaj about 7 years ago - 12 comments

#16 - Breaking in Do Expression

Issue - State: closed - Opened by clemmy about 7 years ago - 1 comment

#15 - Completion values are highly unintuitive with conditionals

Issue - State: closed - Opened by dead-claudia about 7 years ago - 5 comments

#14 - The proposal's use of completion values are highly unintuitive with loops

Issue - State: open - Opened by dead-claudia about 7 years ago - 20 comments

#13 - Special casing class/function declarations to have completion semantics

Issue - State: open - Opened by clemmy over 7 years ago - 3 comments

#12 - switch

Issue - State: closed - Opened by alexisvincent over 7 years ago - 2 comments

#11 - If you treat the statement as an expression, I do not think you need a do-expressions

Issue - State: closed - Opened by kgtkr over 7 years ago - 5 comments

#10 - Can we generate a list with do expressions?

Issue - State: open - Opened by kasperpeulen over 7 years ago - 4 comments

GitHub / tc39/proposal-do-expressions issues and pull requests