Christoffer Lerno
Christoffer Lerno
No, they resolve to 1.5 since Bar needs 1.5+. Different major versions are considered distinct libraries.
Module would be defined in manifest.json / project.json. A simple scheme is saying `-lib foolib` grabs any foolib `-lib [email protected]` means foolib 1.5+ etc: - `[email protected]` version 1.3 to 1.5...
Things like this should be considered: https://www.lucidchart.com/techblog/2017/03/15/package-management-stop-using-version-ranges/
I am not really looking at a package manager. I think downloading dependencies using other means is fine. Because of how C3 libraries work (essentially zip files with some metadata)...
Adding these limited bit sized types has a profound effect on the compiler, the language semantics and the standard library, so we need to find a different solution. I don't...
I probably need to see how it looked before this and see the diff to see what you added.
If you look at: `static inline bool sema_check_asm_arg_const_int(SemaContext *context, AsmInlineBlock *block, AsmInstruction *instr, AsmArgType arg_type, Expr *expr, Expr *int_expr)`, that's where the check happens I believe. Extending that one to...
I made some refactorings right now, they should be straightforward to resolve, you need to pass a `PlatformTarget` around.
Is this ready for review now?
Sorry for being late in reviewing this, I've had a hectic day and then I had to test the last of what I had in dev. I want to say...