Quinton Miller

`QVector.of` will look like this after this patch is rebased onto #108: ```crystal module QVector(T) macro of(*type_args) {% types = type_args.map(&.resolve) %} {% if types == {UInt32} %} {{ Container_QVector_unsigned_int_...

Rebased on top of master. Also there is now special logic to prefer container module names (`TypeConfig#container_type`) over `#crystal_type`, so nested container names can be disambiguated in the `.of` macro...

More specifically it could break code that depends on that return type for type deduction, e.g. instance variables: https://play.crystal-lang.org/#/r/9z1p If `T.f` returns an `Enumerable(Int32)` then any of the `include`s will...

This happens with GitHub itself too, so it should not be used as a guide of correctness: ```crystal # crystal foo(

crystal-lang/crystal#11481 might eventually provide a way to discover true dependencies, including e.g. non-source files loaded from macros, and emit depfiles. Until then the `$(shell find)` approach is probably the most...

SIP is to PyQt5 what Bindgen is to qt5.cr, and it seems they took the second approach: https://github.com/eduardosm/sip-4.19.7/blob/master/siplib/objmap.c Their wrapper structs look rather fat too, despite Python being dynamically typed...

`QStringList` is technically unsupported, because it inherits from `QList` which in turn inherits from `QListSpecialMethods`, where several methods are ultimately defined: ```cpp template struct QListSpecialMethods { }; template struct QListSpecialMethods;...

check if it still happens in 0.2.2

check if it still happens in 0.2.2

`.new` is problematic because it is defined as _the_ constructor by the language, and so it carries a connotation not seen in alternative string representations, namely that the constructed object...