A more aggressive version could add warnings and increasing Thread.sleeps at compile time as the expiry date approaches.
Show this thread
Crazy idea: the UseByDate[Y, M, D] implicit. If you don't want to support your API for more than a year, require implicit evidence of UseByDate[2018, 12, 16]. Needs SIP-23. A macro autogenerates instances up to specified date. Implementation is left as an exercise for the reader.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
licensesing by implicit resolution :O
- End of conversation
New conversation -
-
-
Don't know if crazy or not, but I have seen this done in an actual, real life Ruby project. (With runtime errors, of course.
) -
Now *that* is crazy...
End of conversation
New conversation -
-
-
Can confirm: that idea is crazy (though also fun).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Also, Nats are available today, though you might incur "some" compile slowdown computing the Nat of 2018..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I actually want this for binaries - things that don’t get patched or rebuilt are usually vulnerable to some CVE or zero-day
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I’ve thought of randomly throwing with a probability that grows as the date approaches.
-
Maybe I should offer a variety of aggression strategies at the definition-site... ;)
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.