tc39/proposal-structs

Issues

• Native Equality Support for Structs

  #60 opened a month ago by musicq
  2

• A design for struct module identity

  #59 opened a month ago by guybedford
  0

• Should we allow struct expressions?

  #58 opened 2 months ago by JLHwung
  0

• [Discussion] Better to focus language design efforts on wasm?

  #53 opened 3 months ago by alshdavid
  2

• Potential use case in webGPU

  #18 opened 2 years ago by bakkot
  1

• Is `unsafe` too loose a term?

  #50 opened 3 months ago by rrama
  1

• Promise-returning lock methods?

  #55 opened 3 months ago by dead-claudia
  1

• Suggestion: simpler shared functions

  #56 opened 3 months ago by dead-claudia
  0

• Reader/writer lock?

  #54 opened 3 months ago by dead-claudia
  0

• Performance compared to non-GC structs

  #51 opened 3 months ago by Jamesernator
  2

• Array / record support

  #52 opened 3 months ago by Autumnlight02
  1

• Typo in README.md

  #46 opened 3 months ago by ssousa33-OS
  0

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

  #45 opened 3 months ago by jlandrum
  1

• Currently no way to define structs?

  #37 opened 3 months ago by waldemarhorwat
  7

• Lasting API decisions

  #44 opened 3 months ago by waldemarhorwat
  2

• Different syntax compared to classes. - Take inspiration from rust

  #43 opened 3 months ago by Jordan-Hall
  2

• Can you stamp a private field on a struct?

  #42 opened 3 months ago by bakkot
  0

• Behavior of [[Get]] and [[Set]] not specified

  #39 opened 3 months ago by waldemarhorwat
  7

• `return foo;` from constructor should probably be an error

  #41 opened 3 months ago by rkirsling
  0

• how can i identify a struct, and whether it's shared?

  #23 opened 3 months ago by ljharb
  5

• Potential for more minimalism

  #13 opened 3 months ago by annevk
  14

• Restricting shared memory reads and writes to `unsafe` contexts

  #26 opened 3 months ago by rbuckton
  3

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

  #27 opened 3 months ago by bakkot
  32

• naming for `mutex.lock`/`mutex.tryLock`

  #29 opened 4 months ago by bakkot
  3

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

  #25 opened 4 months ago by projektorius96
  1

• An example for a user-land implementation

  #24 opened 8 months ago by Bnaya
  0

• host integration: SharedMessageQueue or similar

  #22 opened a year ago by Jamesernator
  1

• Can shared structs store SharedArrayBuffer?

  #16 opened 3 years ago by Jamesernator
  4

• Is it not somehow redundant with the record & tuple proposal ?

  #9 opened 3 years ago by lifaon74
  4

• Applying shared structs to existing code is difficult with no member functions

  #17 opened 2 years ago by kbabbitt
  1

• Shared structs vs Serializable/Transferable objects

  #8 opened 3 years ago by Jamesernator
  6

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

  #4 opened 3 years ago by lygstate
  3

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

  #15 opened 3 years ago by eddyw
  0

• Major advantages over manually sealing a class?

  #14 opened 3 years ago by theScottyJam
  4

• Should structs be freezeable?

  #12 opened 3 years ago by takikawa
  1

• Interaction with object references from primitives

  #10 opened 3 years ago by acutmore
  2

• Atomics, shared struct fields, and references

  #6 opened 3 years ago by rbuckton
  4

• Recommend explicit `extends null` for shared structs

  #5 opened 3 years ago by rbuckton
  2

• Also add the capability to support for bit filed or other underlying POD functionals.

  #3 opened 3 years ago by lygstate
  6

• Propose new syntax

  #1 opened 3 years ago by MaxGraey
  12

• Breaking Proxy?

  #2 opened 3 years ago by Jack-Works
  4