Hacker News new | ask | show | jobs
by chubot 3156 days ago
Why don't you just use plain fields, and if you need to change it later, delete the field and go fix all compile errors? That's an easy way to find all usages.

Or are you not talking about a statically-typed language which would find the errors when you temporarily delete a field?

1 comments

You don't always control the code that uses it. You'll have a lot of angry customers if you break all their builds.
well, hopefully they aren't having the library update underneath them without warning. :P