| 02:19 | <Mathieu Hofman> | Yeah we need the metadata. Another param decorator we would have is an `@Awaited`, which would have to be coupled with a `@Async` (name to be bikeshed) method decorator since the param decorator cannot replace the method itself (like how method decorators cannot replace the class itself) |
| 12:54 | <littledan> | Some FFI marshaling scenarios require up-front knowledge of the function parameters incl. data types, string decoding behaviors, etc., that makes extractors a poor fit. |
| 13:13 | <rbuckton> | See the example at https://github.com/tc39/proposal-class-method-parameter-decorators?tab=readme-ov-file#foreign-function-interfaces. If you are passing a JS function as a callback to a native API that will use it as a function pointer, it may need to know the expected data types (e.g., integer widths) ahead of time when marshalling from native to JS. |