Josh Goebel
Josh Goebel
Wow... I still think there is a lot to be confused about here (and I'm conflating `toBe` and `toEqual` above), but I don't think the test names help add much...
I did remove the enumerable definitions for the resistor exercises in case that was giving away a bit too much.
> I think we previously discussed if we should add Stubb's and decided only to have them for the earlier exercises. But that's NOT the case at all, it's *all...
> I can see a future where many exercises start deviating from the problem specifications to have slightly different tests and I'm afraid that's a bit of a pain to...
Not sure I follow. `==` and `eql?` are both accepted Ruby conventions for equality in general, no? I don't think this is a matter where the student has a lot...
> But, either way: @yyyc514 can we solve the student awareness by adding a link about case equality to the Ruby Readme? Does anyone read that stuff? > don't test...
https://github.com/exercism/website-copy/blob/master/tracks/ruby/exercises/clock/mentoring.md Quoting: > A good solution should have the following: > - Implement value-object semantics (immutability, ==/hash/eql? by value) So if that's true, why not lead students there with tests?
> If it's something that can be achieved through some handler code And lines can be drawn one pixel at a time also yet we still have a `line` API......
That's going to be slow I think with cos and sin. :) Isn't there faster ways to plot circle? :)
I'll start: - Highlight.js often has more readable grammar definitions (for non regex wizards) - this is one of the reasons that drew me to it. - Prism seems to...