This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 6dc12881110d26bb952bd0f565623144f10a07b6
tree 68c1a4cf50cc28864cf2b72714508e2524798a62
parent db5a98e6cbb88331a6ce484260e9cce9ba882bcd
tree 68c1a4cf50cc28864cf2b72714508e2524798a62
parent db5a98e6cbb88331a6ce484260e9cce9ba882bcd
... |
... |
|












Congrats on the first commit :-)
He gets straight to business!
Weee
btw, I really like the inline docco sample of the generated method that will be created by #generate_method_for_mime
Shouldn’t you make method_missing private?
@drnic
I hope from this point, every metaprogramming trick will have such comment. I personally find it very hard to read metaprogramming code otherwise.
+1 for human-readable meta comment. It’d certainly be nice to have this used throughout the code base. Great job… and nice first commit.
Expectations are high for wycats’ second commit to Rails. We’ll be watching for it with baited breath.
I’m waiting for the failing test which prevents method_missing from ever being used :)
The inline sample doc is really nice too, sets great precedent. I wonder if there could be a failing test to enforce that too – any call to def inside a class eval must have a trailing comment…
+1 for inline meta comments
Those comments are a great idea. Inspired by this commit I’m adding them in more places through docrails.
This is an awesome blossom.
OMG lulz CONGRATS!!!
In all seriousness, the commented code is cool, more plz