Andrei Markeev
Andrei Markeev
hey! thanks for the update and sorry for the delay with response. NY time, quite hectic 😓 I found some more cases where this problem exists. Will investigate, and get...
definitely a bug, structure name collision. thanks for reporting, I'll fix it!
The fact that float numbers aren't yet supported is stated clearly in both README.md and COVERAGE.md. Their support is in the roadmap. There are tons of other not-yet-supported features too,...
http and sockets are target specific. how I see it: 1. there's **TS2C transpiler** (this project) which is a generic transpiler that doesn't know anything about target platform 2. there...
interesting project! :+1: yes, basically this patching as in `cpatch.js` is more or less what a **TSC target** would do. C FFI is also done in **TSC target**, already possible...
Currently, no, but interesting idea. Let’s keep it open as a feature request.
Yes, good points! There will be a switch at some point so that it is easy to change `int16_t` to `int32_t` or `int64_t`. @pitust has tried changing everything to `int64_t`...
`prototype` is not yet supported. Currently finalizing closures, probably prototypes will be the next step after that.
I guess it's a case of the issue when recursive type inference turns into an infinite loop. I spotted this problem couple days ago, although with a bit different use...
I tested a bit and if I create an expression, I can reuse it to create multiple other queries without any issues. The example you provided, well it doesn't work...