Generic Specialization Name Collision
Original Reporter info from Mantis: Warfley
-
Reporter name: Frederic
Original Reporter info from Mantis: Warfley
- Reporter name: Frederic
Description:
When using using multiple generic classes and specialzing them in function type definitons it results in a name collision. This does not occur when specializing in the class header
The example given shows this behaviour. Controlled via the macro Broken, the type is specialized either in the function definition (which results in the error) or in the class definition (which works fine)
Tested on Arch and Debian with fpc 3.0.4
Mantis conversion info:
- Mantis ID: 36477
- OS: Linux
- Platform: X64
- Version: 3.0.4