"bearophile" <[email protected]> wrote in message 
news:[email protected]...
> Walter Bright:
>
> [about non-nullable types]
>> It's a benefit/cost issue. There are no bug-preventing features that are
>> without cost, the idea is to maximize the ratio.
>
> It surely has a cost (you can see it in the Cyclone language: it's safe 
> but quite fussy, so the costs for the programmer can be high enough to 
> discourage its use), but I have not tried this feature in other languages, 
> so it's not easy for me to measure its costs :-)
>

I was assuming he meant cost of implementing that feature, but maybe you're 
right...? 


Reply via email to