Disqus - Latest Comments for marc_andre

Re: Noinline & Crossline, once for all

Marc-André Lafortune — Thu, 15 Jun 2023 10:26:33 -0000

I remain unconvinced by the example of `crossinline`. The solution is not to mark the parameter with `crossinline` but instead to use `try {} finally {}`, as
the flushing of the logger should also happen if the block throws an exception.

Re: Correct Delegation with Ruby 2.6, 2.7 and 3.0

Marc-André Lafortune — Sun, 14 Feb 2021 12:52:42 -0000

I'm in favor of empowering people and I defer to them to take informed decisions and accept risks.
For example, the risk of a method accepting keyword arguments to no longer accepting them seems negligible to me and far outweighs the ugliness of ruby2_keywords.
We can agree to disagree on the accuracy that some code is "broken" and "incorrect" 😄

Re: Correct Delegation with Ruby 2.6, 2.7 and 3.0

Marc-André Lafortune — Sun, 14 Feb 2021 11:26:39 -0000

You may want to specify that "incorrect" applies only for a generic target. If you know that target accepts keyword arguments then (*a, **o) will work, or if target does not accept any, then (*a) will work.

Re: The Pros and Cons of Ruby Refinements

Marc-André Lafortune — Fri, 20 Nov 2020 22:08:37 -0000

I'm glad to report that all the limitations you list are history. I hope to post about good uses of refinements

Re: Ruby refinements and the sorbet type checker

Marc-André Lafortune — Fri, 20 Nov 2020 21:30:18 -0000

I do hope that Sorbet & RBS have actual support for refinements one day.

BTW, doing `h.reject { |k, _v| k.nil? }` is sinful; it's `O(n)`. Prefer `.except(nil)`, or `tap {|h| h.delete(nil)}` or something...

Re: Top 10 errors from 1000+ Ruby on Rails projects (and how to avoid them)

Marc-André Lafortune — Thu, 20 Dec 2018 13:42:26 -0000

For point #2: You may want to mention one can write `foo&.[](:key)&.[](:other)`, although clearly `dig` is nicer. BTW, the `dig` gem is dead, but my backports gem has it + many others...

Re: yield_self in Ruby 2.5 // Michał Łomnicki

Marc-André Lafortune — Fri, 29 Sep 2017 10:31:39 -0000

Please note that `_` is a special name for unused variables (or any name starting with _). IMO it's best to reserve it for such uses.

Re: How To Write Ruby Faster at the Source Code Level

Marc-André Lafortune — Fri, 22 May 2015 09:54:58 -0000

<shameless plug="">Give my gem "fruity" a spin to compare code. It has a nice API and will estimate how long it should run to eliminate variance if possible</plug>

Re: How To Write Ruby Faster at the Source Code Level

Marc-André Lafortune — Fri, 22 May 2015 09:52:41 -0000

Not sure what is meant by "Ruby has a method built-in to create an array with only keys of that hash". Are you talking about `each_keys`? That method doesn't create an array at all...

Re: How To Write Ruby Faster at the Source Code Level

Marc-André Lafortune — Fri, 22 May 2015 09:50:11 -0000

It can't be accurate to say that `sub` is 50% faster. It if the string isn't found, or if it's found and there are no other characters, it has to take the same time, for example.

Re: How To Write Ruby Faster at the Source Code Level

Marc-André Lafortune — Fri, 22 May 2015 09:48:18 -0000

Not sure what is meant by "tighter scope", or by "Fetch taking a second argument for a block"

Re: How To Write Ruby Faster at the Source Code Level

Marc-André Lafortune — Fri, 22 May 2015 09:45:17 -0000

`array.sample`, is not 15 times faster. It's O(1) vs O(n), so there is no bound to how much faster it is.

Re: Rubyists: Just use double-quoted strings.

Marc-André Lafortune — Thu, 22 Jan 2015 17:24:34 -0000

I was wondering why I got a sudden surge of upvotes for my StackOverflow answer!

As I try to explain, benchmarking this is futile, it's interpreted exactly completely and utterly the same way.

See https://stackoverflow.com/q...

Re: Ruby Tips Part 5

Marc-André Lafortune — Tue, 22 Apr 2014 10:16:04 -0000

Even better than `Hash[]` is `Array#to_h`, introduced in Ruby 2.1

Re: ES7 async functions

Marc-André Lafortune — Fri, 04 Apr 2014 11:37:47 -0000

Checkout IcedCoffeescript...

Re: Technology by FTBpro developers — Ruby 2.1 - Our Experience

Marc-André Lafortune — Thu, 20 Mar 2014 11:59:47 -0000

We're using the FastImage gem which has the advantage of now requiring the full image to be local. YMMV

Re: Technology by FTBpro developers — Ruby 2.1 - Our Experience

Marc-André Lafortune — Thu, 20 Mar 2014 11:58:44 -0000

Thanks, that's reassuring. I was going to ask if this bug had been reported, seemed pretty major to me.

Re: Why I won't squash my commits - # Hash

Marc-André Lafortune — Sun, 09 Feb 2014 12:30:07 -0000

Ouch, I mess up my rebase for sure! Also, I realized that, in the example I gave with 15 commits, the last two should be squashed together...

Re: Stop including Enumerable, return Enumerator instead

Marc-André Lafortune — Thu, 09 Jan 2014 13:03:38 -0000

Not sure why you feel it looks like a hack, it's actually the right way to use `enum_for`. You'll find similar code all over the rubinius codebase, for example.

Re: Stop including Enumerable, return Enumerator instead

Marc-André Lafortune — Thu, 09 Jan 2014 13:01:42 -0000

Good post and your point about "is this class a collection or not" is important.

I'd say that a class that has an `each` method should be a collection and should include `Enumerable`. On the other hand, there are cases where you simply want to have a method that iterates and that method should return an enumerator if no block is given.

This is why I'm not too convinced about your example. Why not add a singleton method to the User called `with_gravatars` instead?

Re: Why I love Ruby Enumerable#inject

Marc-André Lafortune — Thu, 05 Dec 2013 17:59:54 -0000

I'm afraid your second example is a bad example of inject; `each_with_object` should be used instead.
The same thing could be said for your third example...

Re: Let's make a Ruby hash map method that returns a hash instead of an array - Chris Holtz

Marc-André Lafortune — Tue, 10 Sep 2013 17:12:32 -0000

In Ruby 2.1 you'll get Array#to_h so you will be able to do `hash.map{|...| [key, value]}.to_h` to get a hash. See http://bugs.ruby-lang.org/i...

Re: What is the difference between a block, a proc, and a lambda in ruby? - Build, Break, Learn.

Marc-André Lafortune — Fri, 30 Aug 2013 21:16:31 -0000

There are other differences between a Proc and a lambda. Procs will expand a single array parameter (compare with {|a, b = :foo| p a, b}.call([1,2,3]) ) and will also return different arity when they have optional parameters.

Re: Ruby 2.0.0 by example - # Hash [via http://ipv6gate.sixxs.net]

Marc-André Lafortune — Thu, 04 Apr 2013 16:31:43 -0000

Good question, I'm don't know.

Re: Ruby 2.0.0 by example - # Hash [via http://ipv6gate.sixxs.net]

Marc-André Lafortune — Thu, 04 Apr 2013 13:59:47 -0000

No hit if you don't use them, but yes I believe there's a small hit for calls made within a `using SomeRefinement` zone.