tc39/proposal-structs issues and pull requests

#58 - Should we allow struct expressions?

Issue - State: open - Opened by JLHwung 15 days ago

#57 - typo: backtick `this` in struct methods note

Pull Request - State: closed - Opened by JoshuaKGoldberg 15 days ago

#56 - Suggestion: simpler shared functions

Issue - State: open - Opened by dead-claudia about 1 month ago

#55 - Promise-returning lock methods?

Issue - State: closed - Opened by dead-claudia about 1 month ago - 1 comment

#54 - Reader/writer lock?

Issue - State: open - Opened by dead-claudia about 1 month ago

#53 - [Discussion] Better to focus language design efforts on wasm?

Issue - State: open - Opened by alshdavid about 2 months ago - 2 comments

#52 - Array / record support

Issue - State: open - Opened by Autumnlight02 about 2 months ago - 1 comment

#51 - Performance compared to non-GC structs

Issue - State: open - Opened by Jamesernator about 2 months ago - 2 comments

#50 - Is `unsafe` too loose a term?

Issue - State: open - Opened by rrama about 2 months ago - 1 comment

#49 - Tiny syntax change in README.md - syntax highlighting for `this`

Pull Request - State: open - Opened by pbiggar about 2 months ago

#48 - Fix link to ParkingLot

Pull Request - State: open - Opened by regseb about 2 months ago

#47 - docs: fix small typos on the README

Pull Request - State: open - Opened by gdorsi about 2 months ago

#46 - Typo in README.md

Issue - State: open - Opened by ssousa33-OS about 2 months ago

#45 - Keyword bloat consideration - extend class opposed to introduction of new data structure

Issue - State: open - Opened by jlandrum about 2 months ago - 1 comment

#44 - Lasting API decisions

Issue - State: open - Opened by waldemarhorwat about 2 months ago - 2 comments

#43 - Different syntax compared to classes. - Take inspiration from rust

Issue - State: open - Opened by Jordan-Hall about 2 months ago - 2 comments

#42 - Can you stamp a private field on a struct?

Issue - State: open - Opened by bakkot about 2 months ago

#41 - `return foo;` from constructor should probably be an error

Issue - State: open - Opened by rkirsling about 2 months ago

#40 - Add 'Changes to object type' section, draft note regarding 'unsafe' parameter

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

#39 - Behavior of [[Get]] and [[Set]] not specified

Issue - State: closed - Opened by waldemarhorwat about 2 months ago - 7 comments

#38 - Remove struct expressions

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

#37 - Currently no way to define structs?

Issue - State: open - Opened by waldemarhorwat about 2 months ago - 7 comments

#36 - Treat both Proxies and Reflect as unsafe

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

#35 - Treat both Proxies and Reflect as unsafe

Pull Request - State: closed - Opened by rbuckton 2 months ago - 2 comments

#34 - Add support for PR Previews

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

#33 - Add PR previews

Pull Request - State: closed - Opened by rbuckton 2 months ago - 3 comments

#32 - Add `unsafe` blocks

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

#32 - Add `unsafe` blocks

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

#31 - Update README to reflect feature going for stage 2

Pull Request - State: closed - Opened by syg 2 months ago

#30 - Normative: Add Mutex and Condition

Pull Request - State: closed - Opened by syg 2 months ago - 2 comments

#29 - naming for `mutex.lock`/`mutex.tryLock`

Issue - State: open - Opened by bakkot 2 months ago - 3 comments

#28 - Normative: Initial spec draft

Pull Request - State: closed - Opened by syg 3 months ago - 1 comment

#27 - `mutex.lock` should give you a disposable token, rather than the mutex itself being disposable

Issue - State: closed - Opened by bakkot 4 months ago - 32 comments

#27 - `mutex.lock` should give you a disposable token, rather than the mutex itself being disposable

Issue - State: closed - Opened by bakkot 4 months ago - 32 comments

#26 - Restricting shared memory reads and writes to `unsafe` contexts

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

#26 - Restricting shared memory reads and writes to `unsafe` contexts

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

#25 - What about defining no-op (unshared) struct keyword used in tandem with Reflect API ? [REQUESTING A COMMENT]

Issue - State: closed - Opened by projektorius96 5 months ago - 1 comment

#24 - An example for a user-land implementation

Issue - State: open - Opened by Bnaya 7 months ago

#23 - how can i identify a struct, and whether it's shared?

Issue - State: closed - Opened by ljharb 8 months ago - 5 comments

#22 - host integration: SharedMessageQueue or similar

Issue - State: open - Opened by Jamesernator 10 months ago - 1 comment

#21 - Add syntax sketch for `struct` and `shared struct`

Pull Request - State: closed - Opened by rbuckton 11 months ago - 1 comment

#20 - change variable in "Shared fixed-length arrays"

Pull Request - State: closed - Opened by sirenkovladd over 1 year ago

#19 - Add dev trial explainer

Pull Request - State: closed - Opened by syg over 1 year ago

#18 - Potential use case in webGPU

Issue - State: open - Opened by bakkot almost 2 years ago - 1 comment

#17 - Applying shared structs to existing code is difficult with no member functions

Issue - State: open - Opened by kbabbitt almost 2 years ago - 1 comment

#16 - Can shared structs store SharedArrayBuffer?

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

#15 - Can non-shared structs have methods? Is an explicit constructor needed?

Issue - State: open - Opened by eddyw over 2 years ago

#14 - Major advantages over manually sealing a class?

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

#13 - Potential for more minimalism

Issue - State: closed - Opened by annevk about 3 years ago - 14 comments

#12 - Should structs be freezeable?

Issue - State: open - Opened by takikawa about 3 years ago - 1 comment

#11 - Add initial spec infrastructure

Pull Request - State: closed - Opened by takikawa about 3 years ago

#10 - Interaction with object references from primitives

Issue - State: closed - Opened by acutmore about 3 years ago - 2 comments

#9 - Is it not somehow redundant with the record & tuple proposal ?

Issue - State: open - Opened by lifaon74 about 3 years ago - 4 comments

#8 - Shared structs vs Serializable/Transferable objects

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

#7 - Fix typo

Pull Request - State: closed - Opened by CharlyJazz about 3 years ago

#6 - Atomics, shared struct fields, and references

Issue - State: open - Opened by rbuckton over 3 years ago - 4 comments

#5 - Recommend explicit `extends null` for shared structs

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

#4 - Does this are a replacement of https://github.com/tschneidereit/proposal-typed-objects?

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

GitHub / tc39/proposal-structs issues and pull requests