Ashley Claymore

@leoelm from @Bloomberg has begun looking into the changes required for this.

Hi @rbuckton, thanks for taking a look at https://github.com/bloomberg/TypeScript/pull/76. We've merged that now. I'll sync up with @leoelm and hopefully we'll get the PR to Microsoft open tomorrow.

Hi @magic-akari Unless I have misunderstood the issue, this sounds like you might have mixed up two unrelated concepts in JavaScript. `let` and `const` create a "binding" from a name...

Here's an example of how strings (a primitive list vaguely similar to Tuples) currently behave with `let`: ```js const isPrimitive = (v) => Object(v) !== v; assert(isPrimitive("strings")); const a =...

Hi @mikeal, Would you be able to provide some details on how you are hoping to make use of R&T? With the latest feedback we have received from the committee...

Thanks for those details @mlanza! > When records and tuples finally arrive, I won't have to employ this practice anymore. I'll be able use records and tuples instead of objects...

> I'd like to talk to workers without the structured clone overhead or sharedarraybuffer burden You may be interested in https://github.com/tc39/proposal-structs?tab=readme-ov-file#shared-structs

Hi @matthew-dean, this proposal was discussed at the most recent TC39 meeting. The notes for that are available here: https://github.com/tc39/notes/blob/main/meetings/2024-04/april-09.md#discussing-new-directions-for-rt > This would be especially valuable in reactive libraries, like...

I think this is a duplicate of #375 Applying the construction recursively could slow down creating the values, as the original mutable object would be created and then the 2nd...

> I have not find any specification about the truthy / falsy about the tulpe or records. The specification can be found in the ToBoolean abstract operation. https://tc39.es/proposal-record-tuple/#sec-toboolean