- Python
record --from-testskeeps the calls that pass arguments by keyword where Python does
not bind them by position: keyword-only parameters (def f(x, *, flag)) and an argument named
after a skipped default (f(x, fill='*')). They were dropped fromtest-inputs.jsonl; they
are now written with akwargsobject, which the driver already replays. - Python
diffandbenchpass keyword arguments to the Rust bindings under the bindings'
snake_case names (scaleBy=10asscale_by=10); a keyword-only parameter named in camelCase
failed every case withTypeError: unexpected keyword argument. A Python mismatch shows its
keyword arguments after the positional ones, as Ruby's does, so aknown-diffs.jsonlentry
forf(x)no longer explainsf(x, flag=True). - JS/TS
record --from-testsencodes the captured arguments with the codecrecordanddiff
use, instead of a copy of it that had fallen behind. ABufferwas captured as aUint8Array
(sob.toString('hex')recorded"104,105"), aFloat64Arrayor other typed array as an
object with numeric keys, and an object shaped like a marker ({ $date: 'x' }) was replayed as
aDate. A call is now left out, as one that passes a function or a cycle already was, when an
argument is a RegExp, an Error, aURL, anArrayBuffer, a boxed primitive or an object with
toJSON: those were captured as{}, their own fields or theirtoJSONresult, which replay
passed as a different value. A class instance is still captured as its own fields. analyzejudges each export with the same functionsbridgeuses. It had its own copy of
the rules and put units instart_herethatbridgethen refused ("every export ... must
stay in TypeScript/JavaScript"). The copy missed three of them: a JS unit's sibling.d.ts(a
callback declared there), a class method or constructor that takes a function, and a type
alias such astype Pat = RegExp. Such a unit is nowcautionand left out. Both commands
sharebridge::ts_functionsandbridge::class_reason, so in Python, Ruby, Java, Kotlin and
Goanalyzenow also checks class methods.