gem_bench 2.0.2 → 2.0.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 59e1de2253ef3ec5e1a82ee85837764bd4f5bb52e4e1445489d7ae3d28adf5b6
4
- data.tar.gz: '088ee6272de7a10656b202e1a24a29cfc144e0032e218fdb6322552eec416fe5'
3
+ metadata.gz: ba58266e066c47120ecba80dcd81b5aa35cf2e35132e5eb8f8bc62a0cfdcb8b4
4
+ data.tar.gz: 9b491c517466e244b98f8d01152daa213a5947d9de92970abae6ad64076842ef
5
5
  SHA512:
6
- metadata.gz: 98f28036a4f33a517593ed8af78fdf3b177d4033bc58a3e1be55958513ec28e72f24dad753f3c400fa0b35af6b40b85d17026e11fed669862dd2b8d56f7690bc
7
- data.tar.gz: e5334f36e3e534be04804c83ee37eb94810b05aa73fefcb1c39b573f3fdab692ea1f4a9ca5b5a929bdc0a2666dcb591520f8648e412fc30ff3c44bc76c5da9bd
6
+ metadata.gz: 8eb0b66dc41d9913fad9e88599908cf0e1787e01701e64ade5e065ac4428853b726855345704742a9279dc7dba74fef2eea4c7d4eb84495f7cc46438b07051a5
7
+ data.tar.gz: 9f8b0b6419d6c8ffeb0999149a4c7bc797723dd3a4e362025644c83813e4cb5e3c065b4b7e0bcd8e55d941d7ad3a395072510a7895bfe910b3eb8fad0b6627a9
checksums.yaml.gz.sig CHANGED
Binary file
data/CHANGELOG.md CHANGED
@@ -11,9 +11,16 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
11
11
  ### Fixed
12
12
  ### Removed
13
13
 
14
- [2.0.2] SEP.17.2024
14
+ ## [2.0.3] SEP.18.2024
15
+ ### Added
16
+ - More documentation
17
+ ### Fixed
18
+ - Typos in documentation
19
+ - Copyright years
20
+
21
+ ## [2.0.2] SEP.17.2024
15
22
  COVERAGE: 82.15% -- 382/465 lines in 9 files
16
- BRANCH COVERAGE: 58.79% -- 97/165 branches in 9 branches
23
+ BRANCH COVERAGE: 58.79% -- 97/165 branches in 9 files
17
24
  51.72% documented
18
25
  ### Added
19
26
  - CI for Ancient Rubies
@@ -26,7 +33,7 @@ BRANCH COVERAGE: 58.79% -- 97/165 branches in 9 branches
26
33
  - Typo in URL in documentation
27
34
  - Gemspec description & Summary
28
35
 
29
- [2.0.1] SEP.17.2024
36
+ ## [2.0.1] SEP.17.2024
30
37
  COVERAGE: 82.15% -- 382/465 lines in 9 files
31
38
  BRANCH COVERAGE: 58.08% -- 97/167 branches in 9 files
32
39
  51.72% documented
@@ -42,7 +49,7 @@ BRANCH COVERAGE: 58.08% -- 97/167 branches in 9 files
42
49
  ### Fixed
43
50
  - Stopped swallowing `ArgumentError` in certain exceptional cases
44
51
 
45
- [2.0.0] SEP.25.2023
52
+ ## [2.0.0] SEP.25.2023
46
53
  ### Added
47
54
  - Compatible with Bundler 2+
48
55
  - Checksums for release
@@ -60,18 +67,18 @@ BRANCH COVERAGE: 58.08% -- 97/167 branches in 9 files
60
67
  - Removed Appraisals
61
68
  - Removed Travis-CI
62
69
 
63
- [1.0.6] SEP.09.2018
70
+ ## [1.0.6] SEP.09.2018
64
71
  - Documentation improvements
65
72
  - Add Ruby 2.5 to build matrix
66
73
 
67
- [1.0.5] JUN.05.2017
74
+ ## [1.0.5] JUN.05.2017
68
75
  - Allow github macro as an alternative to git within Gemfile for strict version constraint analysis
69
76
 
70
- [1.0.3] JUN.02.2017
77
+ ## [1.0.3] JUN.02.2017
71
78
  - fixed accidental removal of loaded_gems in 1.0.2
72
79
  - better documentation
73
80
 
74
- [1.0.2] JUN.02.2017
81
+ ## [1.0.2] JUN.02.2017
75
82
  - version constraint checking, useful to add a spec enforcing Gemfile version constraints, by Peter Boling
76
83
  - Console use:
77
84
  - GemBench::StrictVersionRequirement.new({verbose: true})
@@ -85,42 +92,42 @@ Rspec.describe("Gemfile") do
85
92
  end
86
93
  ```
87
94
 
88
- [1.0.1] MAR.25.2017
95
+ ## [1.0.1] MAR.25.2017
89
96
  - fixed a typo that prevented Gemfile comparison by mobilutz
90
97
 
91
- [1.0.0] FEB.26.2017
98
+ ## [1.0.0] FEB.26.2017
92
99
  - New feature: scan all code (except for test/spec/feature code) in all loaded gems for a given regex:
93
100
  - puts GemBench.find(look_for_regex: /HERE BE DRAGONS/).starters.map {|gem| "#{gem.name} has DRAGONS at #{gem.stats}" }.join("\n")
94
101
  - Added basic specs
95
102
  - More Documentation
96
103
  - added back git dependency to gemspec (pulled in latest Gem scaffolding from Bundler :/)
97
104
 
98
- [0.0.8] JAN.16.2014
105
+ ## [0.0.8] JAN.16.2014
99
106
  - Corrected issues with 0.0.7 release.
100
107
  - More Documentation
101
108
  - removed git dependency from gemspec
102
109
 
103
- [0.0.7] DEC.23.2013 (Yanked immediately)
110
+ ## [0.0.7] DEC.23.2013 (Yanked immediately)
104
111
  - Attempt to fix failure on encoding problem, with a rescue fallback (Issue #1) by Peter Boling
105
112
  - Readme / Documentation improvements by John Bachir
106
113
  - Runtime output improvements by John Bachir
107
114
 
108
- [0.0.6] AUG.29.2013
115
+ ## [0.0.6] AUG.29.2013
109
116
  - Added license to gemspec by Peter Boling
110
117
  - No longer altering Ruby load path - Let the gem manager do that by Peter Boling
111
118
 
112
- [0.0.5] AUG.28.2013
119
+ ## [0.0.5] AUG.28.2013
113
120
  - Encode as UTF-8 prior to comparison by Peter Boling
114
121
 
115
- [0.0.4] APR.06.2013
122
+ ## [0.0.4] APR.06.2013
116
123
  - Expanded exclusion list by Peter Boling
117
124
 
118
- [0.0.3] APR.06.2013
125
+ ## [0.0.3] APR.06.2013
119
126
  - Late night coding needs more coffee by Peter Boling
120
127
 
121
- [0.0.2] APR.06.2013
128
+ ## [0.0.2] APR.06.2013
122
129
  - Works against 265 dependency Gemfile by Peter Boling
123
130
  - Added ability to evaluate a Gemfile by Peter Boling
124
131
 
125
- [0.0.1] APR.05.2013
132
+ ## [0.0.1] APR.05.2013
126
133
  - Initial release by Peter Boling
data/CODE_OF_CONDUCT.md CHANGED
@@ -1,20 +1,30 @@
1
+
1
2
  # Contributor Covenant Code of Conduct
2
3
 
3
4
  ## Our Pledge
4
5
 
5
- We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+ We as members, contributors, and leaders pledge to make participation in our
7
+ community a harassment-free experience for everyone, regardless of age, body
8
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
9
+ identity and expression, level of experience, education, socio-economic status,
10
+ nationality, personal appearance, race, religion, or sexual identity
11
+ and orientation.
6
12
 
7
- We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
13
+ We pledge to act and interact in ways that contribute to an open, welcoming,
14
+ diverse, inclusive, and healthy community.
8
15
 
9
16
  ## Our Standards
10
17
 
11
- Examples of behavior that contributes to a positive environment for our community include:
18
+ Examples of behavior that contributes to a positive environment for our
19
+ community include:
12
20
 
13
21
  * Demonstrating empathy and kindness toward other people
14
22
  * Being respectful of differing opinions, viewpoints, and experiences
15
23
  * Giving and gracefully accepting constructive feedback
16
- * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
- * Focusing on what is best not just for us as individuals, but for the overall community
24
+ * Accepting responsibility and apologizing to those affected by our mistakes,
25
+ and learning from the experience
26
+ * Focusing on what is best not just for us as individuals, but for the
27
+ overall community
18
28
 
19
29
  Examples of unacceptable behavior include:
20
30
 
@@ -29,56 +39,95 @@ Examples of unacceptable behavior include:
29
39
 
30
40
  ## Enforcement Responsibilities
31
41
 
32
- Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
42
+ Community leaders are responsible for clarifying and enforcing our standards of
43
+ acceptable behavior and will take appropriate and fair corrective action in
44
+ response to any behavior that they deem inappropriate, threatening, offensive,
45
+ or harmful.
33
46
 
34
- Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
47
+ Community leaders have the right and responsibility to remove, edit, or reject
48
+ comments, commits, code, wiki edits, issues, and other contributions that are
49
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
50
+ decisions when appropriate.
35
51
 
36
52
  ## Scope
37
53
 
38
- This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
54
+ This Code of Conduct applies within all community spaces, and also applies when
55
+ an individual is officially representing the community in public spaces.
56
+ Examples of representing our community include using an official e-mail address,
57
+ posting via an official social media account, or acting as an appointed
58
+ representative at an online or offline event.
39
59
 
40
60
  ## Enforcement
41
61
 
42
- Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at peter.boling@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
62
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
63
+ reported to the community leaders responsible for enforcement at
64
+ [INSERT CONTACT METHOD].
65
+ All complaints will be reviewed and investigated promptly and fairly.
43
66
 
44
- All community leaders are obligated to respect the privacy and security of the reporter of any incident.
67
+ All community leaders are obligated to respect the privacy and security of the
68
+ reporter of any incident.
45
69
 
46
70
  ## Enforcement Guidelines
47
71
 
48
- Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
72
+ Community leaders will follow these Community Impact Guidelines in determining
73
+ the consequences for any action they deem in violation of this Code of Conduct:
49
74
 
50
75
  ### 1. Correction
51
76
 
52
- **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
77
+ **Community Impact**: Use of inappropriate language or other behavior deemed
78
+ unprofessional or unwelcome in the community.
53
79
 
54
- **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
80
+ **Consequence**: A private, written warning from community leaders, providing
81
+ clarity around the nature of the violation and an explanation of why the
82
+ behavior was inappropriate. A public apology may be requested.
55
83
 
56
84
  ### 2. Warning
57
85
 
58
- **Community Impact**: A violation through a single incident or series of actions.
86
+ **Community Impact**: A violation through a single incident or series
87
+ of actions.
59
88
 
60
- **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
89
+ **Consequence**: A warning with consequences for continued behavior. No
90
+ interaction with the people involved, including unsolicited interaction with
91
+ those enforcing the Code of Conduct, for a specified period of time. This
92
+ includes avoiding interactions in community spaces as well as external channels
93
+ like social media. Violating these terms may lead to a temporary or
94
+ permanent ban.
61
95
 
62
96
  ### 3. Temporary Ban
63
97
 
64
- **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
98
+ **Community Impact**: A serious violation of community standards, including
99
+ sustained inappropriate behavior.
65
100
 
66
- **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
101
+ **Consequence**: A temporary ban from any sort of interaction or public
102
+ communication with the community for a specified period of time. No public or
103
+ private interaction with the people involved, including unsolicited interaction
104
+ with those enforcing the Code of Conduct, is allowed during this period.
105
+ Violating these terms may lead to a permanent ban.
67
106
 
68
107
  ### 4. Permanent Ban
69
108
 
70
- **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
109
+ **Community Impact**: Demonstrating a pattern of violation of community
110
+ standards, including sustained inappropriate behavior, harassment of an
111
+ individual, or aggression toward or disparagement of classes of individuals.
71
112
 
72
- **Consequence**: A permanent ban from any sort of public interaction within the community.
113
+ **Consequence**: A permanent ban from any sort of public interaction within
114
+ the community.
73
115
 
74
116
  ## Attribution
75
117
 
76
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
77
- available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
78
-
79
- Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
118
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119
+ version 2.0, available at
120
+ [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
80
121
 
81
- [homepage]: https://www.contributor-covenant.org
122
+ Community Impact Guidelines were inspired by
123
+ [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
82
124
 
83
125
  For answers to common questions about this code of conduct, see the FAQ at
84
- https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
126
+ [https://www.contributor-covenant.org/faq][FAQ]. Translations are available
127
+ at [https://www.contributor-covenant.org/translations][translations].
128
+
129
+ [homepage]: https://www.contributor-covenant.org
130
+ [v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
131
+ [Mozilla CoC]: https://github.com/mozilla/diversity
132
+ [FAQ]: https://www.contributor-covenant.org/faq
133
+ [translations]: https://www.contributor-covenant.org/translations
data/CONTRIBUTING.md CHANGED
@@ -4,8 +4,7 @@ Bug reports and pull requests are welcome on GitHub at [https://github.com/pboli
4
4
  This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
5
5
  the [code of conduct][🤝conduct].
6
6
 
7
- To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request
8
- and you might also post a message to the [gitter chat][🏘chat].
7
+ To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request.
9
8
 
10
9
  ## Development
11
10
 
@@ -59,4 +58,3 @@ Made with [contributors-img][🖐contrib-rocks].
59
58
  [🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
60
59
  [🔒️rubygems-checksums-pr]: https://github.com/rubygems/guides/pull/325
61
60
  [🚎src-main]: https://github.com/pboling/gem_bench
62
- [🏘chat]: https://matrix.to/#/%23pboling_gem_bench:gitter.im
data/README.md CHANGED
@@ -63,12 +63,14 @@
63
63
  </div>
64
64
  </div>
65
65
 
66
+ [benchmarking-example]: https://github.com/panorama-ed/memo_wise/pull/339
67
+
66
68
  ## What's it do?
67
69
 
68
70
  🏁 Copy & Re-namespace any gem to benchmark side-by-side with `benchmarks-ips`!
69
71
 
70
72
  👯 For example, many of the ~dozen Memoization gems use the same namespaces (`Memoist`, `Memery`, etc).
71
- In order to compare them side-by-side one of them must be re-namespaced.
73
+ In order to compare them side-by-side one of them must be re-namespaced. ([working example][benchmarking-example])
72
74
 
73
75
  <details>
74
76
  <summary>Scene: Spectator at a game of Ruby Sports Gem Ball</summary>
@@ -87,9 +89,9 @@ Coach:
87
89
 
88
90
  </details>
89
91
 
90
- 🤩 Benchmark trunk against released version of a library!
92
+ 🤩 Benchmark trunk against released version of a library! ([working example][benchmarking-example])
91
93
 
92
- 🧐 A `git clone` build can now be run against the latest public release build, side-by-side, by re-namespacing one of them.
94
+ 🧐 A `git clone` build can now be run against the latest public release build, side-by-side, by re-namespacing one of them. ([working example][benchmarking-example])
93
95
 
94
96
  🕵️‍♀️ Static Gemfile and installed gem library source code analysis.
95
97
  Regex search through all of a project's source code, including installed Bundler dependencies.
@@ -102,13 +104,9 @@ Regex search through all of a project's source code, including installed Bundler
102
104
  | code triage | [![Open Source Helpers](https://www.codetriage.com/pboling/gem_bench/badges/users.svg)](https://www.codetriage.com/pboling/gem_bench) |
103
105
  | homepage | [on Github.com][homepage] |
104
106
  | documentation | [on Rdoc.info][documentation] |
105
- | live chat | [![Join the chat][🏘chati]][🏘chat] |
106
107
  | expert support | [![Get help on Codementor](https://cdn.codementor.io/badges/get_help_github.svg)](https://www.codementor.io/peterboling?utm_source=github&utm_medium=button&utm_term=peterboling&utm_campaign=github) |
107
108
  | `...` 💖 | [![Liberapay Patrons][⛳liberapay-img]][⛳liberapay] [![Sponsor Me][🖇sponsor-img]][🖇sponsor] [![Follow Me on LinkedIn][🖇linkedin-img]][🖇linkedin] [![Find Me on WellFound:][✌️wellfound-img]][✌️wellfound] [![Find Me on CrunchBase][💲crunchbase-img]][💲crunchbase] [![My LinkTree][🌳linktree-img]][🌳linktree] [![Follow Me on Ruby.Social][🐘ruby-mast-img]][🐘ruby-mast] [![Tweet @ Peter][🐦tweet-img]][🐦tweet] [💻][coderme] [🌏][aboutme] |
108
109
 
109
- [🏘chat]: https://matrix.to/#/%23pboling_gem_bench:gitter.im
110
- [🏘chati]: https://badges.gitter.im/Join%20Chat.svg
111
-
112
110
  <!-- 7️⃣ spread 💖 -->
113
111
  [🐦tweet-img]: https://img.shields.io/twitter/follow/galtzo.svg?style=social&label=Follow%20%40galtzo
114
112
  [🐦tweet]: http://twitter.com/galtzo
@@ -247,11 +245,11 @@ You *may not* need to add this gem to your project.
247
245
 
248
246
  Install the gem and add to the application's Gemfile by executing:
249
247
 
250
- $ bundle add active_security
248
+ $ bundle add gem_bench
251
249
 
252
250
  If bundler is not being used to manage dependencies, install the gem by executing:
253
251
 
254
- $ gem install active_security
252
+ $ gem install gem_bench
255
253
 
256
254
  <details>
257
255
  <summary>Installation Options</summary>
@@ -1,5 +1,5 @@
1
1
  module GemBench
2
2
  module Version
3
- VERSION = "2.0.2"
3
+ VERSION = "2.0.3"
4
4
  end
5
5
  end
data.tar.gz.sig CHANGED
Binary file
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gem_bench
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.2
4
+ version: 2.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Peter Boling
@@ -244,34 +244,20 @@ dependencies:
244
244
  - - ">="
245
245
  - !ruby/object:Gem::Version
246
246
  version: '0'
247
- - !ruby/object:Gem::Dependency
248
- name: simplecov
249
- requirement: !ruby/object:Gem::Requirement
250
- requirements:
251
- - - ">="
252
- - !ruby/object:Gem::Version
253
- version: '0'
254
- type: :development
255
- prerelease: false
256
- version_requirements: !ruby/object:Gem::Requirement
257
- requirements:
258
- - - ">="
259
- - !ruby/object:Gem::Version
260
- version: '0'
261
247
  - !ruby/object:Gem::Dependency
262
248
  name: standard
263
249
  requirement: !ruby/object:Gem::Requirement
264
250
  requirements:
265
251
  - - ">="
266
252
  - !ruby/object:Gem::Version
267
- version: 1.35.1
253
+ version: '1.40'
268
254
  type: :development
269
255
  prerelease: false
270
256
  version_requirements: !ruby/object:Gem::Requirement
271
257
  requirements:
272
258
  - - ">="
273
259
  - !ruby/object:Gem::Version
274
- version: 1.35.1
260
+ version: '1.40'
275
261
  description: |-
276
262
  * Benchmark different versions of same or similar gems
277
263
  * Copy & Re-namespace any gem to benchmark side-by-side with `benchmarks-ips`
@@ -304,10 +290,10 @@ licenses:
304
290
  - MIT
305
291
  metadata:
306
292
  homepage_uri: https://railsbling.com/tags/gem_bench/
307
- source_code_uri: http://github.com/pboling/gem_bench/tree/v2.0.2
308
- changelog_uri: http://github.com/pboling/gem_bench/blob/v2.0.2/CHANGELOG.md
293
+ source_code_uri: http://github.com/pboling/gem_bench/tree/v2.0.3
294
+ changelog_uri: http://github.com/pboling/gem_bench/blob/v2.0.3/CHANGELOG.md
309
295
  bug_tracker_uri: http://github.com/pboling/gem_bench/issues
310
- documentation_uri: https://www.rubydoc.info/gems/gem_bench/2.0.2
296
+ documentation_uri: https://www.rubydoc.info/gems/gem_bench/2.0.3
311
297
  wiki_uri: http://github.com/pboling/gem_bench/wiki
312
298
  funding_uri: https://liberapay.com/pboling
313
299
  rubygems_mfa_required: 'true'
metadata.gz.sig CHANGED
Binary file