You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://github.com/danielpclark/faster_path/pulse)
6
+
[](https://github.com/danielpclark/faster_path/pulse)
Here are some addtional stats. From Rails loading to my home page, these methods are called _(not directly, Rails & gems call them)_ this many times. And the home page has minimal content.
58
+
Here are some additional stats. From Rails loading to my home page, these methods are called _(not directly, Rails & gems call them)_ this many times. And the home page has minimal content.
59
59
```ruby
60
60
Pathname#to_s called 29172 times.
61
61
Pathname#<=> called 24963 times.
@@ -97,8 +97,10 @@ I've said this about Sprockets but this required two other gems to be updated as
97
97
## Status
98
98
99
99
* Rust compilation is working
100
-
* Methods are _most likely_ stable
101
-
* Testers and developers are most welcome!
100
+
* Methods are stable
101
+
* Thoroughly tested
102
+
* Testers and developers are most welcome
103
+
* Windows & encoding support is underway!
102
104
103
105
## Installation
104
106
@@ -113,7 +115,7 @@ curl -sSf https://static.rust-lang.org/rustup.sh | sh
113
115
Add this line to your application's Gemfile:
114
116
115
117
```ruby
116
-
gem 'faster_path', '~> 0.2.3'
118
+
gem 'faster_path', '~> 0.3.1'
117
119
```
118
120
119
121
And then execute:
@@ -184,7 +186,7 @@ These will **not** be included by default in monkey-patches. Be cautious when u
184
186
|`FasterPath.basename`|`File.basename`|
185
187
186
188
It's been my observation (and some others) that the Rust implementation of the C code for `File` has similar results but
187
-
performance seems to vary based on CPU cache on possibly 64bit/32bit system environmnets. When these methods were initially written, and somewhat simplistic, they were faster than the C implementations on `File`. After the implementations have been perfected to match the behavior in Ruby they don't perform as well and are therefore not included by default when the monkey patch method `FasterPath.sledgehammer_everything!` is executed. If you don't want to pass the `WITH_REGRESSION` environment variable you can put any turthy parameter on the monkey patch method to include it.
189
+
performance seems to vary based on CPU cache on possibly 64bit/32bit system environments. When these methods were initially written, and somewhat simplistic, they were faster than the C implementations on `File`. After the implementations have been perfected to match the behavior in Ruby they don't perform as well and are therefore not included by default when the monkey patch method `FasterPath.sledgehammer_everything!` is executed.
188
190
189
191
## Getting Started with Development
190
192
@@ -205,13 +207,7 @@ Learn and share performance tips on the [wiki](https://github.com/danielpclark/f
205
207
206
208
### Building and running tests
207
209
208
-
First, bundle the gem's development dependencies by running `bundle`.
209
-
210
-
Then, build the rust code:
211
-
212
-
```sh
213
-
rake build_src
214
-
```
210
+
First, bundle the gem's development dependencies by running `bundle`. Rust compilation is included in the current rake commands.
215
211
216
212
FasterPath is tested with [The Ruby Spec Suite](https://github.com/ruby/spec) to ensure it is compatible with the
217
213
native implementation, and also has its own test suite testing its monkey-patching and refinements functionality.
0 commit comments