typed-objects-explainer

typed-objects-explainer copied to clipboard

Overloading of []

1

There is `[]` overloading mentioned [here](https://github.com/nikomatsakis/typed-objects-explainer/blob/master/overloading.md). As I understand it, `.` can't be overloaded because we should have possibility to use object properties, right? `[]` shouldn't be overloadable as well...

chicoxyzzy

To support Wasm, we'll need some notion of an immutable field: once initialized it cannot be written. A couple of obvious possibilities for how to denote an immutable field are:...

lars-t-hansen

In this example: ``` int8(128) // returns 127 int8("128") // returns 127 ``` Shouldn't it be `-127` instead as per conversion rules of C, Int8Array and many others?

RReverser

Given these structs: ``` js const Point = new StructType({ x: float64, y: float64 }); const Series = new StructType(Point, 100); const Line = new StructType({ from: Point.ref, to: Point.ref...

phpnode

new StructType() vs makeStruct()

12

I'm implementing a typed objects library (not yet released) and trying to follow the proposals here as closely as possible so that one day it can be made compatible with...

phpnode

Memory order?

4

The given example `var PointType = new StructType({x: float64, y: float64})` uses an object to specify which types are supposed to be used and what their attribute keys are. But...

CoDEmanX

typeof on a value type

2

Should probably yield `symbol.toString()` where `symbol` is the defining symbol. This is because @tschneidereit thinks that returning a non-string will break the web.

nikomatsakis

We should support some extension of class syntax that lets you define new struct/value types.

nikomatsakis

Things about how to implement uint64_t and int64_t

1

w

lygstate

Add Record, Tuple, Map, and Set

2

Sebastien Markbage suggested the addition of four kinds of value types: - Record - Tuple - Map - Set These are all things that conceptually could be built on what...

nikomatsakis