Among the many flame-wars in the developer community is the one about typing: static vs. dynamic.
In Ruby, we can have the best of both worlds, via gem contracts.
I was going to write about this powerful and flexible gem here, but on second thought will just link to this excellent page by the gem's author.
For further actions, you may consider blocking this person and/or reporting abuse
sylvance -
Stephen Margheim -
Lucian Ghinda -
Cherry Ramatis -
Once suspended, burdettelamar will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, burdettelamar will be able to comment and publish posts again.
Once unpublished, all posts by burdettelamar will become hidden and only accessible to themselves.
If burdettelamar is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Burdette Lamar.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag burdettelamar:
Unflagging burdettelamar will restore default visibility to their posts.
Top comments (2)
I'd be interested to hear your experiences with the gem. Have you found it makes it easier to write applications? Do you write fewer tests? Do you use it everywhere in a codebase or only in particular places?
Thanks, Phil.
Using contracts makes it easier to catch bugs earlier: type error is caught immediately rather than further downstream where it's harder to debug.
For my large-scale in-house test frameworks, I've used it throughout.
For code that will become a gem, though, I don't use it, because it creates a dependency that the potential user might find unacceptable.