Dan Sugalski wrote: > And, unless Larry objects, I feel that all vtable methods should have > the option of going with a 'scalar native' form if the operation if it's > determined at runtime that two scalars are the same type, though this is > optional and bay be skipped for cost reasons. (Doing it with, for > example, complex numbers might be worth it, or when expensive > conversions might be avoided) just a quick comment on complex numbers. i would have thought the idea would be to treat them as pairs? ie (Real Part, Imaginary Part). this would mean that the standard things that are being done for ints etc would also benefit complex numbers. the only things worth considering at this level might be ways of optimising pair operations for efficency? Anyway, i'm not sure that complex numbers is really an internals issue? peter
- Re: standard representations Dan Sugalski
- public domain? (was Re: standa... Bradley M. Kuhn
- Re: standard representations Bradley M. Kuhn
- Re: standard representations Andy Dougherty
- Re: standard representations Jarkko Hietaniemi
- Re: standard representations Dan Sugalski
- licensing issues (was Re: stan... Bradley M. Kuhn
- Re: standard representations Uri Guttman
- Re: standard representations Dan Sugalski
- Re: standard representations Dan Sugalski
- Re: standard representations Peter Buckingham
- Re: standard representations Dan Sugalski
- Re: standard representations Nick Ing-Simmons
- Re: standard representations Dan Sugalski
- Re: standard representations Benjamin Stuhl
- Re: standard representations Dan Sugalski
- Re: standard representations Andy Dougherty
- Re: standard representations Benjamin Stuhl
- Re: standard representations Dan Sugalski
- Re: standard representations Nicholas Clark
- Re: standard representations Nick Ing-Simmons