A unary plus before X'..' keeps the blob, as SQLite drops the plus. Bare default words take non-ASCII characters and a later dollar sign, as SQLite identifiers do. The comment-after-e fixture uses 0x1e--, which SQLite creates.
SQLite accepts a `CREATE TABLE` with no spaces between its parts, and reading one went wrong in three ways. A constraint written straight after a type (`REAL(8)CHECK(...)`) became part of the type, which changed how the column's values were read (REAL as INTEGER, BLOB as TEXT). A quoted type straight after a column name (`id"INTEGER" PRIMARY KEY`) became part of the name, so the column wasn't seen as the row's key. And `DEFAULT-5`, `STRICT;` or `WITHOUT ROWID;` weren't recognised. Names, types and clauses are now split wherever SQLite splits them, and only its five whitespace characters count as space.
Follow-up to #2080. `nint`, `nuint` and `dynamic` are only keywords when nothing in scope has that name, but a conversion operator to a program's own type called `nint` or `dynamic` was read as the built-in and reported as missing; such a name is now looked up among the program's types first. An explicit `System.IntPtr` keeps meaning the built-in. And a conversion to `List<String>` where `String` is another namespace's type, imported without `using System;`, is matched to that type before `String` is tried as `string`.
Follow-up to #2076, which stopped a program's own `App.String` being read as `string` but left two conversion operators unmatched against a .NET program's metadata: one to `System.Collections.Generic.List<String>`, and one to `String` in a type that also converts to an unrelated `Other.String`. A short type name in a conversion target is now looked up first in the enclosing types and namespaces among the types the program has; only when nothing there has that name is it read as the built-in (`String` as `string`).
- Strip `global::` and convert metadata `/` nested-type separators in `norm_type`
as well as `norm_type_qualified` so method parameters taking nested or
`global::`-qualified types reconcile without mismatch.
- Emit `ref ` only for leading `ref` modifiers followed by whitespace and a type
start, avoiding spurious spaces inside identifiers containing `ref` or on `@ref`
value types.
- Keep non-`System` types named like CLR built-ins (such as `App.String`) distinct
from C# built-in keywords in qualified conversion-target comparisons.
- Collapse multi-dimensional zero-lower-bound CLI array shapes (`[0...,0...]`) to
C# rank commas (`[,]`) while preserving rank-1 `[0...]` and non-zero/sized bounds.
SQLite lets table constraints follow each other without a comma (`UNIQUE(v) PRIMARY KEY(id)`) and lets a key column sit in extra parentheses (`PRIMARY KEY((id))`). Both the rowid-alias check and the WITHOUT ROWID key layout now find the primary key in those forms, so rows from such tables show their key values in the right columns.
Follow-up to #2049. A conversion operator whose target type is named `@checked` was read as a checked operator with no target type, because the `@` was lost before the name was compared with the `checked` keyword. The keyword is now recognised only when it was written without `@`.
In an Apple keyed archive, a string whose bytes were stored as a reference to another object was shown as raw data, and a date stored as a whole number of seconds was not shown as a date. References are now followed, within the existing byte and node limits, and integer times are formatted as dates.
The SquashFS reader ended the inode table at the directory table and the directory table at the fragment or id table. An image with an export or xattr table in between, or with its tables in another order, was read past the table's end and reported as damaged. Each table now ends at the nearest following table of the six, or at the end of the filesystem.
A C# member or parameter named with a verbatim identifier (`@class`, `@namespace`, `@event`, `@operator`) had its `@` dropped and was then read as the keyword, which opened fake scopes and changed member kinds. Verbatim identifiers are now kept as names and never matched as keywords or modifiers.
An Android manifest flag stored as an integer (`exported` = 0, `debuggable` = 1) was read as not set, so a component marked not exported could be reported as exported. Integer-typed values are now read as booleans as Android does, and only the un-namespaced `package` attribute names the package.
* Use shared packet capture and per-frame protocol inspection
* Pin PCAP inspection to merged shared library
* Test shared PCAP truncation and public adapter parity
* Use shared WebAssembly inspection with app error compatibility
* Cover WASM resource indexes and component partial reports against oracle
* deps: pin craft-libs to the merged shared revision