Value world, object, tuple literals, const

.chronus/changes/feature-object-literals-2024-2-15-18-36-3.md

@@ -0,0 +1,17 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@typespec/compiler"
+---
+
+New Language Feature: Object and Tuple Literals.
+
+```tsp
+@dummy(#{
+  name: "John",
+  age: 48,
+  address: #{ city: "London" }
+  aliases: #["Bob", "Frank"]
+})
+```

.chronus/changes/feature-object-literals-2024-2-18-22-23-26.md

@@ -0,0 +1,10 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@typespec/json-schema"
+  - "@typespec/protobuf"
+  - "@typespec/versioning"
+---
+
+Update to support new value types

.chronus/changes/feature-object-literals-2024-3-16-10-38-3.md

@@ -0,0 +1,24 @@
+---
+changeKind: deprecation
+packages:
+  - "@typespec/compiler"
+---
+
+Decorator API: Legacy marshalling logic
+
+  If a library had a decorator with `valueof` one of those types `numeric`, `int64`, `uint64`, `integer`, `float`, `decimal`, `decimal128`, `null` it used to marshall those as JS `number` and `NullType` for `null`. With the introduction of values we have a new marshalling logic which will marshall those numeric types as `Numeric` and the others will remain numbers. `null` will also get marshalled as `null`.
+
+  For now this is an opt-in behavior with a warning on decorators not opt-in having a parameter with a constraint from the list above.
+
+  Example: 
+  ```tsp
+  extern dec multipleOf(target: numeric | Reflection.ModelProperty, value: valueof numeric);
+  ```
+  Will now emit a deprecated warning because `value` is of type `valueof string` which would marshall to `Numeric` under the new logic but as `number` previously.
+
+  To opt-in you can add the following to your library js/ts files.
+  ```ts
+  export const $flags = defineModuleFlags({
+    decoratorArgMarshalling: "lossless",
+  });
+  ```

.chronus/changes/feature-object-literals-2024-3-16-11-58-32.md

@@ -0,0 +1,7 @@
+---
+changeKind: feature
+packages:
+  - "@typespec/openapi3"
+---
+
+Add support for new object and tuple literals as default values (e.g. `decimals: decimal[] = #[123, 456.7];`)

.chronus/changes/feature-object-literals-2024-3-16-12-0-15.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - "@typespec/rest"
+---
+
+Update types to support new values in TypeSpec

.chronus/changes/feature-object-literals-2024-3-16-17-54-23.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: feature
+packages:
+  - "@typespec/html-program-viewer"
+---
+
+Add support for new fields added with the value world

.chronus/changes/feature-object-literals-32024-2-15-18-36-3.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@typespec/http"
+---
+
+Update Flow Template to make use of the new tuple literals

docs/language-basics/values.md

@@ -0,0 +1,125 @@
+---
+id: values
+title: Values
+---
+
+# Values
+
+TypeSpec can define values in addition to types. Values are useful in an API description to define default values for types or provide example values. They are also useful when passing data to decorators, and for template parameters that are ultimately passed to decorators.
+
+There are three kinds of values: objects, arrays, and scalars. These values can be created with object literals, array literals, and scalar literals and initializers. Additionally, values can result from referencing enum members and union variants.
+
+## Object values
+
+Object values use the syntax `#{}` and can define any number of properties. For example:
+
+```typespec
+const point = #{ x: 0, y: 0 };
+```
+
+The object value's properties must refer to other values. It is an error to reference a type.
+
+```typespec
+const example = #{
+  prop1: #{ nested: true }; // ok
+  prop2: { nested: true }; // error: values can't reference a type
+  prop3: string; // error: values can't reference a type
+}
+```
+
+## Array values
+
+Array values use the syntax `#[]` and can define any number of items. For example:
+
+```typespec
+const points = #[#{ x: 0, y: 0 }, #{ x: 1, y: 1 }];
+```
+
+As with object values, array values cannot contain types.
+
+If an array type defines a minimum and maximum size using the `@minValue` and `@maxValue` decorators, the compiler will validate that the array value has the appropriate number of items. For example:
+
+```typespec
+/** Can have at most 3 tags */
+@maxItems(2)
+model Tags is Array<string>;
+
+const exampleTags1: Tags = #["TypeSpec", "JSON"]; // ok
+const exampleTags2: Tags = #["TypeSpec", "JSON", "OpenAPI"]; // error
+```
+
+## Scalar values
+
+There are two ways to create scalar values: with a literal syntax like `"string value"`, and with a scalar initializer like `utcDateTime.fromISO("2020-12-01T12:00:00Z")`.
+
+### Scalar literals
+
+The literal syntax for strings, numerics, booleans and null can evaluate to either a type or a value depending on the surrounding context of the literal. When the literal is in _type context_ (a model property type, operation return type, alias definition, etc.) the literal becomes a literal type. When the literal is in _value context_ (a default value, property of an object value, const definition, etc.), the literal becomes a value. When the literal is in an _ambiguous context_ (e.g. an argument to a template or decorator that can accept either a type or a value) the literal becomes a value. The `typeof` operator can be used to convert the literal to a type in such ambiguous contexts.
+
+```typespec
+extern dec setNumberValue(target: unknown, color: valueof numeric);
+extern dec setNumberType(target: unknown, color: numeric);
+extern dec setNumberTypeOrValue(target: unknown, color: numeric | (valueof numeric));
+
+@setNumberValue(123) // Passes the scalar value `numeric(123)`.
+@setNumberType(123) // Passes the numeric literal type 123.
+@setNumberTypeOrValue(123) // passes the scalar value `numeric(123)`.
+model A {}
+```
+
+### Scalar initializers
+
+Scalar initializers create scalar values by calling an initializer with one or more values. Scalar initializers for types extended from `numeric`, `string`, and `boolean` are called by adding parenthesis after the scalar reference:
+
+```typespec
+const n = int8(100);
+const s = string("hello");
+```
+
+Any scalar can additionally be declared with named initializers that take one or more value parameters. For example, `utcDateTime` provides a `fromISO` initializer that takes an ISO string. Named scalars can be declared like so:
+
+```typespec
+scalar ipv4 extends string {
+  init fromInt(value: uint32);
+}
+
+const ip = ipv4.fromInt(2341230);
+```
+
+## Enum member &amp; union variant references
+
+References to enum members and union variants can be either types or values and follow the same rules as scalar literals. When an enum member reference is in _type context_, the reference becomes an enum member type. When in _value context_ or _ambiguous context_ the reference becomes the enum member's value.
+
+```typespec
+extern dec setColorValue(target: unknown, color: valueof string);
+extern dec setColorMember(target: unknown, color: Reflection.EnumMember);
+
+enum Color {
+  red,
+  green,
+  blue,
+}
+
+@setColorValue(Color.red) // same as passing the literal "red"
+@setColorMember(Color.red) // passes the enum member Color.red
+model A {}
+```
+
+When a union variant reference is in _type context_, the reference becomes the type of the union variant. When in _value context_ or _ambiguous context_ the reference becomes the value of the union variant. It is an error to refer to a union variant whose type is not a literal type.
+
+```typespec
+extern dec setColorValue(target: unknown, color: valueof string);
+extern dec setColorType(target: unknown, color: string);
+
+union Color {
+  red: "red",
+  green: "green",
+  blue: "blue",
+  other: string,
+}
+
+@setColorValue(Color.red) // passes the scalar value `string("red")`
+@setColorValue(Color.other) // error, trying to pass a type as a value.
+@setColorType(Color.red) // passes the string literal type `"red"`
+model A {}
+```

docs/libraries/http/reference/decorators.md

@@ -358,7 +358,7 @@ it will be used as a prefix to the route URI of the operation.
 `@route` can only be applied to operations, namespaces, and interfaces.
 
 ```typespec
-@TypeSpec.Http.route(path: valueof string, options?: (anonymous model))
+@TypeSpec.Http.route(path: valueof string, options?: { shared: boolean })
 ```
 
 #### Target