Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / tc39/proposal-wavy-dot issues and pull requests

#15 - Shouldn't `a~.name(b)` as an expression statement also delegate to *SendOnly?

Issue - State: closed - Opened by dead-claudia over 3 years ago - 2 comments

#14 - This has some overlap with the pipeline operator proposal

Issue - State: open - Opened by dead-claudia almost 4 years ago

#13 - Add a badge for specifying current stage

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

#12 - Clearly specify `LeftHandSideExpression`

Issue - State: open - Opened by michaelfig about 4 years ago - 1 comment

#11 - The wavy-dot may encourage unnecessary chaining promise

Issue - State: open - Opened by JLHwung about 4 years ago

#10 - How to chain Promise#catch to the eventual handler?

Issue - State: open - Opened by JLHwung about 4 years ago

#9 - Need safer expansion

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

#8 - Composition with optional chaining

Issue - State: open - Opened by kesne over 5 years ago - 3 comments

#7 - add capn-proto. De-italicize promise

Pull Request - State: closed - Opened by erights over 5 years ago

#6 - Why not add methods first, and gain adoption, before syntax?

Issue - State: open - Opened by ljharb over 5 years ago - 1 comment

#5 - Why is a new promise API needed at all? Why REST?

Issue - State: open - Opened by devsnek over 5 years ago - 16 comments

#4 - Actual operator character

Issue - State: closed - Opened by michaelfig over 5 years ago - 22 comments

#3 - Should handler methods be optional?

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

#2 - Explain Promise Pipelining

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

#1 - Minimal Promise.prototype methods?

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