koparasy wrote: > tivation is that `canPassInRegisters`, `hasTrivialDestructor`, and > `recordAlignInBytes` aren't really properties of the type. They're properties > of how this translation unit chose to lay the type
Thanks for adding me here. I am leaning towards @xlauko opinion on this. Mainly because: > These three fields are TU properties, not type properties, and belong at > module scope? We do not support yet purely heterogeneous modules, and the approach I took (on incubator) was to nest them in regions, so practically both solutions would work, but conceptually these are not type properties and we should not bound them to types. https://github.com/llvm/llvm-project/pull/188300 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
