[haXe] Type inferrence problem
Michael Pliskin
pl at tepkom.ru
Wed Aug 2 08:52:09 CEST 2006
Hello Nicolas,
NC> True. This is not a problem impossible to resolve, but it has some
NC> serious implementation issues, since the code generated when it's a
NC> property will vary (in that case it will actually be a call to
NC> Xml.getNodeValue() ). And since the type infered was { nodeValue :
NC> String } you also have to be sure that it was not used *before* with
NC> another value. Quite tricky actually.
I see... Well yes, really tricky. I don't think it is a number one
or even number two priority, but it'd be nice to fix once since
implicitly typed anonymous functions like this one are really
convenient when doing tasks like xml parsing, and explicit typing
for all of these will make the code a lot less readable...
--
Best regards,
Michael mailto:pl at tepkom.ru
More information about the Haxe
mailing list