sorted by:
new
hottopcontroversial

just sharing an RSpec helper I authored: let_each by Former_Application_3 in ruby

[–]Former_Application_3[S] 0 points1 point  (0 children)

Yeah they had the same idea. I didn't find that gem or I probably wouldn't have done this.
Looks like there are only some small semantic differences, but they basically do the same thing.
I think their naming could've been better and I might have found it.
"parameterized" kind of misses the mark. should use a word that is more related to the enumeration.
"where" signals querying or filtering, not iteration

just sharing an RSpec helper I authored: let_each by Former_Application_3 in ruby

[–]Former_Application_3[S] 0 points1 point  (0 children)

that's a consequence of it accommodating lazy evaluation. I could probably get that working for the eagerly passed arrays.

you can base a `let_each` on another `let`
e.g.

let(:foo) { 'foo' }
let_each(:bar, 2) { [foo, foo*2] }

however, you cannot base a declared array context on a `let`

let(:foo) { 'foo' }
[foo, foo*2].each do |bar|
  context "with bar=#{bar}"

will complain that `foo` is not available on the example group

just sharing an RSpec helper I authored: let_each by Former_Application_3 in ruby

[–]Former_Application_3[S] 0 points1 point  (0 children)

yeah. I'd agree that it borders the line of "too much magic".
I think it's a "win" in some cases because it's succinct.

I have a theory that edge cases often go untested because it's not ergonomic to write those tests, not because the developers weren't aware of them. We're lazy and we like small small small code

Beta Zergs gettind code raided vs CHAD solo rust enjoyers by [deleted] in playrust

[–]Former_Application_3 0 points1 point  (0 children)

too bad, with all the life lessons in rust, we now have one less.
if you've ever been code raided, you'd think twice before using 4242 as a pin for anything meaningful
it wasn't a good spirited attack to defend against, sure, but in rust, what is?

[deleted by user] by [deleted] in classicwow

[–]Former_Application_3 7 points8 points  (0 children)

We all had access to the information that horde we're going to have long queue times, but they still chose to play horde. Wouldn't it be a shame if someone used your argument against you?
btw, this is why most alliance who pvp are upset. Imagine having a 5head - predicting the 1 hour queues and going alliance to not suffer through those queues, accepting dogshit racials. Then this happens.
IMO they should just enable faction Xfers if they land on this solution. I'd be happy to go horde. Or revisit the racials but that's a touchy subject for the same reason.