Ecosyste.ms: Issues

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

GitHub / arthurfiorette/proposal-try-operator issues and pull requests

#72 - TryResult<T> extends Array<unknown> without implementation of its methods

Issue - State: closed - Opened by DScheglov 10 days ago - 5 comments

#71 - Rename `Result` class to `TryResult`

Pull Request - State: open - Opened by Arlen22 11 days ago - 1 comment

#70 - Update spec.emu and add me to the author list

Pull Request - State: open - Opened by Arlen22 11 days ago - 1 comment

#69 - Brainstorming the user-facing experience

Issue - State: open - Opened by Arlen22 11 days ago - 6 comments

#68 - [Question] What about `finally` and more advanced flows?

Issue - State: open - Opened by Judekeyser 20 days ago - 2 comments

#66 - Editorial recommendations for README

Pull Request - State: closed - Opened by garretmh 24 days ago - 1 comment

#65 - Rewrite proposal to use AssignmentExpression

Pull Request - State: closed - Opened by Arlen22 24 days ago

#64 - Are void operations necessary?

Issue - State: closed - Opened by Arlen22 25 days ago - 3 comments

#63 - There is no conflict with the using proposal, but they relate

Issue - State: closed - Opened by Arlen22 25 days ago - 5 comments

#62 - Assignment to existing variables must be addressed

Issue - State: closed - Opened by Arlen22 25 days ago - 6 comments

#61 - The new proposal should be called "safe assignment expression"

Issue - State: closed - Opened by Arlen22 25 days ago - 12 comments

#60 - Fix for desugaring: keeping reference mutability intact

Pull Request - State: closed - Opened by DScheglov 25 days ago - 1 comment

#59 - Link to issue 30 in readme

Issue - State: closed - Opened by rbalicki2 25 days ago - 2 comments

#57 - [ImgBot] Optimize images

Pull Request - State: closed - Opened by imgbot[bot] 26 days ago

#56 - Fix error references in try expressions example

Pull Request - State: closed - Opened by senocular 26 days ago - 1 comment

#55 - why are parens required?

Issue - State: closed - Opened by ljharb 26 days ago - 5 comments

#54 - these are statements, not expressions

Issue - State: closed - Opened by ljharb 26 days ago - 29 comments

#53 - Rewrite into `try-expressions`

Pull Request - State: closed - Opened by arthurfiorette 27 days ago - 3 comments

#52 - multiple same titles.

Pull Request - State: closed - Opened by akaramanapp about 2 months ago - 1 comment

#51 - How can I use it in my nextJs project

Issue - State: closed - Opened by pasternak-karmel 3 months ago - 2 comments

#50 - Runtime implementation and its availability

Issue - State: closed - Opened by thodnev 5 months ago - 7 comments

#49 - Why error first?

Issue - State: closed - Opened by yishayhaz 5 months ago - 11 comments

#49 - Why error first?

Issue - State: closed - Opened by yishayhaz 5 months ago - 11 comments

#48 - Example implementation using Typescript

Issue - State: open - Opened by Arlen22 5 months ago - 5 comments

#47 - feat: Safe assignment polyfill V2, introducing Function#result() method

Pull Request - State: closed - Opened by otaxhu 5 months ago - 1 comment

#46 - what about `throw;` (and `throw undefined || null || 0 || false || "";`)

Issue - State: closed - Opened by Arlen22 5 months ago - 3 comments

#45 - async functions already allow this pattern, but only asyncly

Issue - State: closed - Opened by Arlen22 5 months ago - 6 comments

#43 - Counter proposal : type safe try/catch

Issue - State: open - Opened by y-nk 5 months ago - 13 comments

#42 - Propose an alternative syntax for try assign

Pull Request - State: closed - Opened by troglodytto 5 months ago - 1 comment

#41 - Prior art to safe assignment operator proposal

Issue - State: open - Opened by coderaiser 5 months ago - 4 comments

#40 - How does this improve upon Promises?

Issue - State: closed - Opened by JamesRamm 5 months ago - 5 comments

#39 - `?=` violates the type safety of `await`

Issue - State: closed - Opened by alray2569 6 months ago - 4 comments

#38 - Unexpected parsing inconsistency

Issue - State: closed - Opened by alray2569 6 months ago - 1 comment

#37 - The assignment operator should not have the responsibility of flow control

Issue - State: closed - Opened by rafageist 6 months ago - 4 comments

#36 - Try catch example

Issue - State: closed - Opened by jorge-melnik 6 months ago

#35 - This doesn't accomplish anything

Issue - State: closed - Opened by alray2569 6 months ago - 20 comments

#34 - Using Colon

Issue - State: closed - Opened by itsabgr 6 months ago - 3 comments

#33 - Reconsidering the Need for a New Operator in Error Handling Proposals

Issue - State: closed - Opened by rafageist 6 months ago - 29 comments

#32 - Miscellaneous criticisms

Issue - State: closed - Opened by DavidJCobb 6 months ago - 3 comments

#31 - Write-Once `const` Declarations proposal is a possible alternative

Issue - State: closed - Opened by zaygraveyard 6 months ago - 2 comments

#30 - Tuples/Objects and Falsy errors.

Issue - State: closed - Opened by arthurfiorette 6 months ago - 83 comments
Labels: enhancement

#29 - Why `null`?

Issue - State: closed - Opened by sindresorhus 6 months ago - 6 comments
Labels: enhancement

#28 - Let's talk on 25/Aug 16 UTC!

Issue - State: closed - Opened by arthurfiorette 6 months ago - 5 comments

#26 - Dont use two identifiers, just catch thrown errors

Issue - State: closed - Opened by KevsRepos 6 months ago - 4 comments

#25 - Fix Lea's first name

Pull Request - State: closed - Opened by mAAdhaTTah 6 months ago

#24 - Alternative Approach: Implementing Safe Assignment Without ?= Operator

Issue - State: closed - Opened by rafageist 6 months ago - 12 comments

#21 - feat: add TypeScript definitions, allow falsy errors, and refine erro…

Pull Request - State: closed - Opened by valentinpolitov 6 months ago - 3 comments

#20 - More complex async function example

Issue - State: closed - Opened by zaverden 6 months ago - 2 comments

#19 - How can I contribute this is a really cool idea

Issue - State: closed - Opened by dolev146 6 months ago - 6 comments

#18 - Object methods not supported

Issue - State: closed - Opened by robbiespeed 6 months ago - 2 comments

#17 - As-is, it is impossible to accurately refine types in a generic context

Issue - State: closed - Opened by rbalicki2 6 months ago - 6 comments

#16 - Error propagation

Issue - State: closed - Opened by nikolalukovic 6 months ago - 6 comments

#15 - Have you read the "Try-catch oneliner" proposal from 2019?

Issue - State: open - Opened by mmkal 6 months ago - 2 comments

#14 - implicit await promises

Issue - State: closed - Opened by smeijer 6 months ago - 1 comment

#13 - re: Why Not data First?

Issue - State: closed - Opened by smeijer 6 months ago - 16 comments
Labels: documentation

#12 - Special-casing particular expression types is a footgun

Issue - State: closed - Opened by pie-flavor 6 months ago - 3 comments

#11 - any idea to re-use the same error variable?

Issue - State: closed - Opened by opensas 6 months ago - 11 comments

#8 - Poll requires X account

Issue - State: closed - Opened by jbkly 6 months ago - 3 comments

#7 - Syntax overkill in basic example

Issue - State: closed - Opened by Akiyamka 6 months ago - 1 comment

#6 - Please re-consider the "recursive unwrapping" design aspect

Issue - State: closed - Opened by getify 6 months ago - 9 comments
Labels: enhancement

#5 - Question: Why Symbol.result in addition to throw?

Issue - State: closed - Opened by garretmh 6 months ago - 22 comments
Labels: enhancement

#4 - Discussion: Preferred operator/keyword for safe assignment

Issue - State: closed - Opened by Not-Jayden 6 months ago - 131 comments

#3 - Suggestion: Return a discriminable object instead of a tuple array

Issue - State: closed - Opened by Not-Jayden 6 months ago - 25 comments

#2 - [ImgBot] Optimize images

Pull Request - State: closed - Opened by imgbot[bot] 6 months ago

#1 - Backward compatible implementation

Issue - State: closed - Opened by alfredosalzillo 6 months ago - 1 comment