2 Apr
2010
2 Apr
'10
3:45 a.m.
On 2 April 2010 07:22, Twan van Laarhoven
As a simple approximation, you could consider functions without type signatures to have changed if their implementation or any function they depend on has changed.
Ah, too much work. Having libraries where the exported functions have signature seems more desirable than no signatures (documentation benefit, at least). So a tool could just print a warning "No type signature for _export-name_". This would be an effective social obligation to encourage people to add signatures to exported functions. Also other developers could see the library wasn't using export signatures and be cautious about depending on it themselves. Best wishes Stephen