HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gogotanaka
Rubype
Ruby2015–2015
gogotanaka / Rubype

Rubype

:dromedary_camel: Super simple, clean. Contracts for Ruby

2Distinct people
2Mentions
0Explicit recommenders
375GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:dromedary_camel: Super simple, clean. Contracts for Ruby

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2015-04-09 02:10:47 UTC to 2015-04-09 04:16:06 UTC.

012015-04-09 02:00:00 UTC to 2015-04-09 03:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 9, 02:002015-04-09 03:00:00 UTC to 2015-04-09 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 9, 03:002015-04-09 04:00:00 UTC to 2015-04-09 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 9, 04:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 9, 02:002015-04-09 02:00:00 UTC2015-04-09 03:00:00 UTC110
Apr 9, 03:002015-04-09 03:00:00 UTC2015-04-09 04:00:00 UTC000
Apr 9, 04:002015-04-09 04:00:00 UTC2015-04-09 05:00:00 UTC101

What Hacker News says

2 sources
Really cool idea! I like that you can specify a `#respond_to?` constraint instead of a class. Not sure if OP is the author, but here's some feedback: * It would be better if this didn't pollute the global namespace by defining `#typesig` in `Module` [0] -- perhaps consider refactoring that method into a module which the user may extend. Doing so would also get you out of needing to define `Module#prepend` for older versions of Ruby. * Perhaps allow the user to enable/disable type checking at a global/class level. For example, then users could only enable type checking during specs if they wanted. * Instead of using class-level variables, try using class level instance variables. They have less odd behavior when dealing with subclasses [1]. [0] https://github.com/gogotanaka/Rubype/blob/develop/lib/rubype... [1] http://www.sitepoint.com/cla
Read the rest
In Gradual type checking for Ruby

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.