[erlang-questions] Type Specs Preserved in Beam Code

[Tim Watson]

Current type specs are only available in beam code if you compile it with debug_info or use the 'abstract_code' parse transform that's floating around on the internet. What are the chances of getting the type spec information preserved in the beam (in a separate chunk) without having to do this? Is this a change to the parser, the compiler, or to the modules dealing with Core - good question there: are type specs supported in Core? - or all of these? If this is low priority I'll happily take it away and try to write a patch, but I'd need a hint about where to start.

Cheers,
Tim