52 Matching Annotations
  1. Last 7 days
  2. Feb 2020
    1. Returns an indication of the number of arguments accepted by a method. Returns a nonnegative integer for methods that take a fixed number of arguments. For Ruby methods that take a variable number of arguments, returns -n-1, where n is the number of required arguments. Keyword arguments will be considered as a single additional argument, that argument being mandatory if any keyword argument is mandatory. For methods written in C, returns -1 if the call takes a variable number of arguments.

      What they fail to mention is that apparently the arity is always -1 if the method is available dynamically (due to respond_to_missing?).

  3. Jan 2020
    1. I've often wished for some standard variable to use for blocks and such. Like some people here, I had considered it. Usually I use _ but I know that means "unused" to many/most programmers. I like the % option that Clojure has.

  4. Dec 2019
  5. Nov 2019
    1. Example of someone else defining a file that simply requires another file because this is the one that gem (?) or bundler (?) looks for when your gem is named activerecord-pg_enum

  6. Oct 2019
  7. Sep 2019
  8. Aug 2019
  9. Feb 2019
  10. Jan 2016
    1. require 'active_record/connection_adapters/postgis_adapter/railtie'

      The following worked better in my setup:

      require 'active_record/connection_adapters/postgis/railtie'
    1. with another instance as its receiver

      An instance can call private methods of another instance of the same class.

  11. Nov 2015
    1. まぶた)

      Testing a highlight on Ruby text.

      Highlight is meant to wrap this image: kanji

      Highlight is also meant to include the super-script hiragana characters: まぶた

      Actual highlight includes the hiragana characters "まぶた" as well as ")"

  12. Jul 2015
  13. May 2015
    1. Just to focus on the differences between lambdas and Procs, a lambda acts more like a real method. What does that mean?

      Apparently it means a lambda is less ($@(#$ insane.

    2. When you create your own function to accept procs, the guts need to change a little bit because you'll need to use #call instead of yield inside (because which proc would yield run if you had more than one?).

      Too much special!! Why the special cases? Just so that one can type yield instead of invoking a function and naming the argument?

    3. Use that block of code (now called a Proc) as an input to a function by prepending it with an apersand &

      Oh, Ruby. This is entirely too confusing. Why is the ampersand required to signify that something is passed as a block, especially given that it has a type (Proc)? What does it mean if the ampersand isn't used?