procer 0.1 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0a3d342db7f48f642cbf023a55a7a508012471e015805d96a9e3583871116f80
-  data.tar.gz: 4119f171e84df62fc7497554af445ae492aa985b26d74a51372b9a94548a574e
+  metadata.gz: d3839f7c654ff0e80881ead31ea6a4ddfb75969f07ed640e79a51034c5002298
+  data.tar.gz: 1e992239045802735804b40e628f23c0cbf3c84c67d1e90662e2b22963daf0d6
 SHA512:
-  metadata.gz: 744015e76d9cb4ff18d0ee8463ad7b135af4b0fd1058a312089fc9f62034b6d350913c177cc2720b5082c01b911cd2fd98d9df132c76a930c414b1d402f24313
-  data.tar.gz: 650405168717419f3a6740b14afea0f825740a7a2f7bb98337becd9b636b55bf7e62aa1ef51b8ef5183a6dc1a67d5d477cbcf24ea386259de4e0ec132735abda
+  metadata.gz: f398b858c487391979c4d8b32470187a4dc3cb612d5c14ee2cd875f6de7995479ea98f7239834868cbe525160b816fb3b8e9a23cc20f2f58f9942cb447196a7f
+  data.tar.gz: 76d5eabd79f9eae5a4a23bbf5ed66dc4f0b612904de27e1cd48d4f76532ae520d9c9742008e7309f8711abee5bf7f3e11e68574b6bb51a7655147546622782cf

metadata

@@ -1,42 +1,45 @@
 --- !ruby/object:Gem::Specification
 name: procer
 version: !ruby/object:Gem::Version
-  version: '0.1'
+  version: 0.1.1
 platform: ruby
 authors:
 - Jesús Gómez
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-10-01 00:00:00.000000000 Z
+date: 2023-03-05 00:00:00.000000000 Z
 dependencies: []
-description: "# Procer\n\nA reasonable good default `to_proc` method for all objects.\n\nWhe
+description: "# Procer\n\n**NOTE: Experimental. Use it to experience what a default
+  `to_proc`\ncould have been. For production code, I recommend an explicit\ntransformation,
+  like the one provided by the gem `jgomo3-func`**.\n\nA reasonable good default `to_proc`
+  method for all objects.\n\nInstall with:\n\n```\ngem install procer\n```\n\nWhen
   you require Procer, all objects will have a default `to_proc`\nmethod which will
   try to call one of the following methods, in the\ngiven order:\n\n - `call`\n -
-  `[]`\n - `===`\n \n Many methods which receive a block, can benefit greatlly from
+  `[]`\n - `===`\n \n Many methods which receive a block, can benefit greatly from
   this\n because you can now pass an object to perform the block role.\n \n Think
-  of the Enumerable module and all it's methods.\n \n Many objects define `===`, but
-  not `to_proc`. So they will be nicelly\n usable in a `case/when` expression, but
+  of the Enumerable module and all its methods.\n \n Many objects define `===`, but
+  not `to_proc`. So they will be nicely\n usable in a `case/when` expression, but
   not in other contexts.\n \n This is the case of classes and ranges, which you can
   use in\n `case/when` expressions, but they don't define `to_proc`.\n \n Now they
   do define `to_proc` so they are useful in those contexts.\n \n Examples:\n \n ```ruby\n
   require 'procer'\n \n[1, 2, '3', '4', 5, 6].filter(&Numeric)\n# => [1, 2, 5, 6]\n\n[-10,
   100, -2, 3, 20, -33].filter(&(0..50))\n# => [3, 20]\n```\n\nAlso, Hashes already
-  implement `to_proc` and that is really useful\nwith enumerator. We can use it as
-  a transformation table with `map`:\n\n```ruby\n\ntable = {\n  1 => 'one',\n  2 =>
-  'two',\n  3 => 'three'\n}\n\n[3, 1, 2].map(&table)\n# => ['three, 'one, 'two']\n```\n\nSadly,
-  Arrays, even when they have the same interface as hashes as a\nfunction of indices,
-  don't implement `to_proc` and so they can't be used\nin the same way. Until now.\n\n```ruby\ntable
-  = ['zero', 'one', 'two']\n[2, 0, 1].map(&table)\n# => ['two', 'zero', 'one']\n```\n\nAlternativaly
-  you could have use `values_at`:\n\n```ruby\ntable.values_at([3, 1, 2]) # In the
+  implement `to_proc` and that is useful\nwith Enumerator. We can use it as a transformation
+  table with `map`:\n\n```ruby\n\ntable = {\n  1 => 'one',\n  2 => 'two',\n  3 =>
+  'three'\n}\n\n[3, 1, 2].map(&table)\n# => ['three, 'one, 'two']\n```\n\nSadly, Arrays,
+  even when they have the same interface as hashes as a\nfunction of indices, don't
+  implement `to_proc` and so they can't be used\nin the same way. Until now.\n\n```ruby\ntable
+  = ['zero', 'one', 'two']\n[2, 0, 1].map(&table)\n# => ['two', 'zero', 'one']\n```\n\nAlternatively,
+  you could have used `values_at`:\n\n```ruby\ntable.values_at([3, 1, 2]) # In the
   Hash example\ntable.values_at([2, 0, 1]) # In the Array example\n```\n\nBut the
   map solution is more generic and `table` can be anything that\nimplements `to_proc`
-  and not something that necesarilly implement\n`values_at`.\n\nNotice that if the
-  object implements `[]` that will triumph over\n`===`.  It was expected when I tried
-  to use Integers as the object, as\nthey implement `[]` as a way to access it's binary
-  form:\n\n```ruby\n5 # b101\n[5[2], 5[1], 5[0]] # [1, 0, 1]\n```\n\nSo the proc will
-  work like that:\n\n```ruby\n[2, 4, 5].map(&5)\n# Actual => [1, 0, 0]\n# I was expecting
-  => [false, false, true]\n```\n"
+  and not something that necessarily implements\n`values_at`.\n\nNotice that if the
+  object implements `[]` that will triumph over\n`===`.  It was unexpected when I
+  tried to use Integers as the object, as\nthey implement `[]` as a way to access
+  their binary form:\n\n```ruby\n5 # b101\n[5[2], 5[1], 5[0]] # [1, 0, 1]\n```\n\nSo
+  the proc will work like that:\n\n```ruby\n[2, 4, 5].map(&5)\n# Actual => [1, 0,
+  0]\n# I was expecting => [false, false, true]\n```\n"
 email: jgomo3@gmail.com
 executables: []
 extensions: []
@@ -46,7 +49,10 @@ files:
 homepage: https://github.com/jgomo3/procer/
 licenses:
 - MIT
-metadata: {}
+metadata:
+  'Intended Audience :: Programmers': classifier
+  'Intended Audience :: Developers': classifier
+  'Topic :: Programming :: Experimental': classifier
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -62,7 +68,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.3
+rubygems_version: 3.1.4
 signing_key: 
 specification_version: 4
 summary: Provides a reasonable good default `to_proc` method to all objects