David Blass

This would allow constraints like: ```ts type("", ["t", "k"]); ``` As is, this would fail to parse as t is not considered in scope when parsing a constraint.

With the changes made following `2.0.0-beta.2`, the following type now leads to a TS crash: ```ts const $ = scope({ filename: "0

Up until `2.0.0-beta.2`, this test was passing: ```ts it("referenced in scope inline", () => { const $ = scope({ one: "1", // now is a circular reference error orOne: ()...

This could avoid transitive type resolution issues as detailed in https://github.com/arktypeio/arktype/issues/1031

To ensure normalized strucutre, a UnionNode is not allowed to have `UnionNode` children, and a MorphNode is not allowed to have a `MorphNode` as it's `in` or `out` validator. This...

For now, without the ArkDark extension, you will not completions for definigions like `"string | num"` unless you explicitly opt into the following setting in VSCode: ```json "editor.quickSuggestions": { "strings":...

Would allow parsing the equivalent syntax from TS: ```ts const array = type("", "t[]"); // unknown[] const a = array(); // string[] const b = array("string"); const types = scope({...

Currently in `arktype` and `@arktype/schema`, there are lots of `RawX` and `InternalX` style types that represent inner objects. There is also a `.internal` prop on the external object that allows...

Currently, the rules about where aliases (for cyclic types) can occur are not strict enough, leading to confusing structures where you don't know when you're going to get an alias...

```ts const t = type("string", "=>", (s) => s as any); // currently this fails because it is inferred as `(In: string) => any` attest(t.infer); ``` This is due to...