rust/ripgrep
1
0
Fork 0
mirror of https://github.com/BurntSushi/ripgrep.git synced 2024-12-02 02:56:32 +02:00
Code Issues Releases Activity
df469fe1b4
ripgrep/Cargo.lock

418 lines
18 KiB
Plaintext
Raw Normal View History

commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "aho-corasick"
deps: update all deps
2017-12-30 22:48:25 +02:00
version = "0.6.4"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all deps
2017-12-30 22:48:25 +02:00
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
name = "ansi_term"
deps: update clap, atty, libc Nothing to see here. Note that we continue to refrain to update tempdir, which means we are still bringing in rand 0.4 and rand 0.3. Updating tempdir brings in an old version of remove_dir_all, which in turn brings in winapi 0.2. No thanks.
2018-03-14 04:36:02 +02:00
version = "0.11.0"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update clap, atty, libc Nothing to see here. Note that we continue to refrain to update tempdir, which means we are still bringing in rand 0.4 and rand 0.3. Updating tempdir brings in an old version of remove_dir_all, which in turn brings in winapi 0.2. No thanks.
2018-03-14 04:36:02 +02:00
dependencies = [
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
[[package]]
name = "atty"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
version = "0.2.10"
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update everything
2017-10-22 01:42:34 +02:00
"termion 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
]
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
[[package]]
name = "bitflags"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
version = "1.0.3"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
[[package]]
name = "bytecount"
deps: update bytecount This improves performance with current nightly rustc.
2018-01-30 23:34:30 +02:00
version = "0.3.1"
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Actually use simd/avx optimizations in bytecount crate. Also update compile script.
2016-11-06 04:44:33 +02:00
dependencies = [
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"simd 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
Actually use simd/avx optimizations in bytecount crate. Also update compile script.
2016-11-06 04:44:33 +02:00
]
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
[[package]]
name = "cfg-if"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
version = "0.1.3"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
name = "clap"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
version = "2.31.2"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update clap, atty, libc Nothing to see here. Note that we continue to refrain to update tempdir, which means we are still bringing in rand 0.4 and rand 0.3. Updating tempdir brings in an old version of remove_dir_all, which in turn brings in winapi 0.2. No thanks.
2018-03-14 04:36:02 +02:00
"ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"atty 0.2.10 (registry+https://github.com/rust-lang/crates.io-index)",
"bitflags 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
argv: update clap to 2.29.4 We use the new AppSettings::AllArgsOverrideSelf to permit all flags to be specified multiple times. This removes the need for our previous work-around where we would enable `multiple` for every flag and then just extract the last value when consuming clap's matches. We also add a couple regression tests that ensure repeated switches and flags work as expected.
2018-02-06 02:22:44 +02:00
"strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to latest clap release This also bumps the minimum Rust version required to 1.20.
2017-12-30 22:47:19 +02:00
"textwrap 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2016-12-24 15:32:32 +02:00
"unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
]
Add parallel recursive directory iterator. This adds a new walk type in the `ignore` crate, `WalkParallel`, which provides a way for recursively iterating over a set of paths in parallel while respecting various ignore rules. The API is a bit strange, as a closure producing a closure isn't something one often sees, but it does seem to work well. This also allowed us to simplify much of the worker logic in ripgrep proper, where MultiWorker is now gone.
2016-11-06 03:44:15 +02:00
[[package]]
name = "crossbeam"
Update crossbeam to 0.3.2
2018-01-06 14:29:53 +02:00
version = "0.3.2"
Add parallel recursive directory iterator. This adds a new walk type in the `ignore` crate, `WalkParallel`, which provides a way for recursively iterating over a set of paths in parallel while respecting various ignore rules. The API is a bit strange, as a closure producing a closure isn't something one often sees, but it does seem to work well. This also allowed us to simplify much of the worker logic in ripgrep proper, where MultiWorker is now gone.
2016-11-06 03:44:15 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
[[package]]
name = "encoding_rs"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.7.2"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"cfg-if 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
"simd 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
]
Rework glob sets. We try to reduce the pressure on regexes and offload some of it to Aho-Corasick or exact lookups.
2016-09-16 04:06:04 +02:00
[[package]]
name = "fnv"
deps: update all deps
2017-12-30 22:48:25 +02:00
version = "1.0.6"
Rework glob sets. We try to reduce the pressure on regexes and offload some of it to Aho-Corasick or exact lookups.
2016-09-16 04:06:04 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
[[package]]
name = "fuchsia-zircon"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.3.3"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"bitflags 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
]
[[package]]
name = "fuchsia-zircon-sys"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.3.3"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "glob"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
[[package]]
name = "globset"
globset: release 0.4.0
2018-04-21 18:09:15 +02:00
version = "0.4.0"
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
dependencies = [
deps: update all deps
2017-12-30 22:48:25 +02:00
"aho-corasick 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)",
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
"glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
"regex 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "grep"
grep: release 0.1.8
2018-02-11 20:35:54 +02:00
version = "0.1.8"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
"regex 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"regex-syntax 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
Move all gitignore matching to separate crate. This PR introduces a new sub-crate, `ignore`, which primarily provides a fast recursive directory iterator that respects ignore files like gitignore and other configurable filtering rules based on globs or even file types. This results in a substantial source of complexity moved out of ripgrep's core and into a reusable component that others can now (hopefully) benefit from. While much of the ignore code carried over from ripgrep's core, a substantial portion of it was rewritten with the following goals in mind: 1. Reuse matchers built from gitignore files across directory iteration. 2. Design the matcher data structure to be amenable for parallelizing directory iteration. (Indeed, writing the parallel iterator is the next step.) Fixes #9, #44, #45
2016-10-12 01:57:09 +02:00
]
[[package]]
name = "ignore"
ignore: release 0.4.2
2018-04-21 18:10:16 +02:00
version = "0.4.2"
Move all gitignore matching to separate crate. This PR introduces a new sub-crate, `ignore`, which primarily provides a fast recursive directory iterator that respects ignore files like gitignore and other configurable filtering rules based on globs or even file types. This results in a substantial source of complexity moved out of ripgrep's core and into a reusable component that others can now (hopefully) benefit from. While much of the ignore code carried over from ripgrep's core, a substantial portion of it was rewritten with the following goals in mind: 1. Reuse matchers built from gitignore files across directory iteration. 2. Design the matcher data structure to be amenable for parallelizing directory iteration. (Indeed, writing the parallel iterator is the next step.) Fixes #9, #44, #45
2016-10-12 01:57:09 +02:00
dependencies = [
Update crossbeam to 0.3.2
2018-01-06 14:29:53 +02:00
"crossbeam 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
globset: release 0.4.0
2018-04-21 18:09:15 +02:00
"globset 0.4.0",
deps: bump lazy_static to 1
2017-11-30 18:51:06 +02:00
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
"regex 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"same-file 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"thread_local 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
ignore: fix performance regression on Windows This commit fixes a performance regression in Windows that resulted from fallout from fixing #705. In particular, we introduced an additional stat call for every single directory entry, which can be quite disastrous for performance. There is a corresponding companion PR that fixes the same bug in walkdir: https://github.com/BurntSushi/walkdir/pull/96 Fixes #820
2018-02-21 02:32:58 +02:00
"walkdir 2.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "lazy_static"
version = "1.0.0"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "libc"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
version = "0.2.40"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "log"
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
version = "0.4.1"
deps: upgrade to memchr 2
2017-10-22 00:45:39 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"cfg-if 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: upgrade to memchr 2
2017-10-22 00:45:39 +02:00
]
[[package]]
name = "memchr"
deps: update all deps
2017-12-30 22:48:25 +02:00
version = "2.0.1"
bump various versions
2016-12-30 22:43:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
bump various versions
2016-12-30 22:43:29 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "memmap"
deps: bump memmap to 0.6.2 This removes the last dependency that required winapi 0.2. ripgrep now only depends on winapi 0.3.
2018-01-30 00:09:01 +02:00
version = "0.6.2"
bump bytecount to 0.2 Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
2017-11-13 20:55:41 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
[[package]]
name = "num_cpus"
deps: update all deps
2017-12-30 22:48:25 +02:00
version = "1.8.0"
deps: update everything
2017-10-22 01:42:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
]
[[package]]
name = "rand"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
]
deps: update everything
2017-10-22 01:42:34 +02:00
[[package]]
name = "redox_syscall"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.1.37"
deps: update everything
2017-10-22 01:42:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "redox_termios"
version = "0.1.1"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"redox_syscall 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
[[package]]
name = "regex"
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
version = "1.0.1"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all deps
2017-12-30 22:48:25 +02:00
"aho-corasick 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"regex-syntax 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"thread_local 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
Update to regex 0.2.
2016-12-30 23:24:09 +02:00
"utf8-ranges 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
[[package]]
name = "regex-syntax"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
version = "0.6.0"
deps: update regex crate This update brings with it a new feature of the regex crate which will now use SIMD optimizations automatically at runtime with no necessary compile time flags. All that's needed is to enable the `unstable` feature. Other crates, such as bytecount and encoding_rs, are still using the old-style SIMD support, so we leave the simd-accel and avx-accel features. However, the binaries we distribute on Github no longer have those features enabled, which makes them truly portable. Fixes #135
2018-03-10 21:02:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ucd-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
[[package]]
name = "remove_dir_all"
deps: update remove_dir_all
2018-04-21 18:13:16 +02:00
version = "0.5.1"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
[[package]]
name = "ripgrep"
release: 0.8.1
2018-02-21 03:19:03 +02:00
version = "0.8.1"
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
dependencies = [
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"atty 0.2.10 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update bytecount This improves performance with current nightly rustc.
2018-01-30 23:34:30 +02:00
"bytecount 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"clap 2.31.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"encoding_rs 0.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
globset: release 0.4.0
2018-04-21 18:09:15 +02:00
"globset 0.4.0",
grep: release 0.1.8
2018-02-11 20:35:54 +02:00
"grep 0.1.8",
ignore: release 0.4.2
2018-04-21 18:10:16 +02:00
"ignore 0.4.2",
deps: bump lazy_static to 1
2017-11-30 18:51:06 +02:00
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: bump memmap to 0.6.2 This removes the last dependency that required winapi 0.2. ripgrep now only depends on winapi 0.3.
2018-01-30 00:09:01 +02:00
"memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
"regex 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"same-file 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
termcolor: release 0.3.6
2018-03-26 23:28:21 +02:00
"termcolor 0.3.6",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
]
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
[[package]]
name = "same-file"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "1.0.2"
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "simd"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
version = "0.2.2"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Pass the simd-accel feature to encoding_rs
2017-08-20 08:35:02 +02:00
[[package]]
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
name = "strsim"
argv: update clap to 2.29.4 We use the new AppSettings::AllArgsOverrideSelf to permit all flags to be specified multiple times. This removes the need for our previous work-around where we would enable `multiple` for every flag and then just extract the last value when consuming clap's matches. We also add a couple regression tests that ensure repeated switches and flags work as expected.
2018-02-06 02:22:44 +02:00
version = "0.7.0"
Pass the simd-accel feature to encoding_rs
2017-08-20 08:35:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
name = "tempdir"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
version = "0.3.7"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"rand 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update remove_dir_all
2018-04-21 18:13:16 +02:00
"remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
Completely re-work colored output and tty handling. This commit completely guts all of the color handling code and replaces most of it with two new crates: wincolor and termcolor. wincolor provides a simple API to coloring using the Windows console and termcolor provides a platform independent coloring API tuned for multithreaded command line programs. This required a lot more flexibility than what the `term` crate provided, so it was dropped. We instead switch to writing ANSI escape sequences directly and ignore the TERMINFO database. In addition to fixing several bugs, this commit also permits end users to customize colors to a certain extent. For example, this command will set the match color to magenta and the line number background to yellow: rg --colors 'match:fg:magenta' --colors 'line:bg:yellow' foo For tty handling, we've adopted a hack from `git` to do tty detection in MSYS/mintty terminals. As a result, ripgrep should get both color detection and piping correct on Windows regardless of which terminal you use. Finally, switch to line buffering. Performance doesn't seem to be impacted and it's an otherwise more user friendly option. Fixes #37, Fixes #51, Fixes #94, Fixes #117, Fixes #182, Fixes #231
2016-11-20 18:14:52 +02:00
name = "termcolor"
termcolor: release 0.3.6
2018-03-26 23:28:21 +02:00
version = "0.3.6"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
dependencies = [
wincolor: release 0.1.6
2018-02-11 20:38:00 +02:00
"wincolor 0.1.6",
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
]
deps: update everything
2017-10-22 01:42:34 +02:00
[[package]]
name = "termion"
version = "1.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"redox_syscall 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update everything
2017-10-22 01:42:34 +02:00
"redox_termios 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
[[package]]
name = "textwrap"
deps: update to latest clap release This also bumps the minimum Rust version required to 1.20.
2017-12-30 22:47:19 +02:00
version = "0.9.0"
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2016-10-30 04:27:29 +02:00
[[package]]
name = "thread_local"
deps: update all deps
2017-12-30 22:48:25 +02:00
version = "0.3.5"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update all deps
2017-12-30 22:48:25 +02:00
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
bump deps
2017-08-24 01:52:13 +02:00
"unreachable 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2016-10-30 04:27:29 +02:00
]
deps: update regex crate This update brings with it a new feature of the regex crate which will now use SIMD optimizations automatically at runtime with no necessary compile time flags. All that's needed is to enable the `unstable` feature. Other crates, such as bytecount and encoding_rs, are still using the old-style SIMD support, so we leave the simd-accel and avx-accel features. However, the binaries we distribute on Github no longer have those features enabled, which makes them truly portable. Fixes #135
2018-03-10 21:02:06 +02:00
[[package]]
name = "ucd-util"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
name = "unicode-width"
update deps
2016-12-24 15:32:32 +02:00
version = "0.1.4"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps
2016-10-30 04:27:29 +02:00
[[package]]
name = "unreachable"
bump deps
2017-08-24 01:52:13 +02:00
version = "1.0.0"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "utf8-ranges"
Update to regex 0.2.
2016-12-30 23:24:09 +02:00
version = "1.0.0"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps
2016-10-30 04:27:29 +02:00
[[package]]
name = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "walkdir"
ignore: fix performance regression on Windows This commit fixes a performance regression in Windows that resulted from fallout from fixing #705. In particular, we introduced an additional stat call for every single directory entry, which can be quite disastrous for performance. There is a corresponding companion PR that fixes the same bug in walkdir: https://github.com/BurntSushi/walkdir/pull/96 Fixes #820
2018-02-21 02:32:58 +02:00
version = "2.1.4"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"same-file 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "winapi"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.3.4"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.4.0"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.4.0"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Completely re-work colored output and tty handling. This commit completely guts all of the color handling code and replaces most of it with two new crates: wincolor and termcolor. wincolor provides a simple API to coloring using the Windows console and termcolor provides a platform independent coloring API tuned for multithreaded command line programs. This required a lot more flexibility than what the `term` crate provided, so it was dropped. We instead switch to writing ANSI escape sequences directly and ignore the TERMINFO database. In addition to fixing several bugs, this commit also permits end users to customize colors to a certain extent. For example, this command will set the match color to magenta and the line number background to yellow: rg --colors 'match:fg:magenta' --colors 'line:bg:yellow' foo For tty handling, we've adopted a hack from `git` to do tty detection in MSYS/mintty terminals. As a result, ripgrep should get both color detection and piping correct on Windows regardless of which terminal you use. Finally, switch to line buffering. Performance doesn't seem to be impacted and it's an otherwise more user friendly option. Fixes #37, Fixes #51, Fixes #94, Fixes #117, Fixes #182, Fixes #231
2016-11-20 18:14:52 +02:00
[[package]]
name = "wincolor"
wincolor: release 0.1.6
2018-02-11 20:38:00 +02:00
version = "0.1.6"
Completely re-work colored output and tty handling. This commit completely guts all of the color handling code and replaces most of it with two new crates: wincolor and termcolor. wincolor provides a simple API to coloring using the Windows console and termcolor provides a platform independent coloring API tuned for multithreaded command line programs. This required a lot more flexibility than what the `term` crate provided, so it was dropped. We instead switch to writing ANSI escape sequences directly and ignore the TERMINFO database. In addition to fixing several bugs, this commit also permits end users to customize colors to a certain extent. For example, this command will set the match color to magenta and the line number background to yellow: rg --colors 'match:fg:magenta' --colors 'line:bg:yellow' foo For tty handling, we've adopted a hack from `git` to do tty detection in MSYS/mintty terminals. As a result, ripgrep should get both color detection and piping correct on Windows regardless of which terminal you use. Finally, switch to line buffering. Performance doesn't seem to be impacted and it's an otherwise more user friendly option. Fixes #37, Fixes #51, Fixes #94, Fixes #117, Fixes #182, Fixes #231
2016-11-20 18:14:52 +02:00
dependencies = [
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
Completely re-work colored output and tty handling. This commit completely guts all of the color handling code and replaces most of it with two new crates: wincolor and termcolor. wincolor provides a simple API to coloring using the Windows console and termcolor provides a platform independent coloring API tuned for multithreaded command line programs. This required a lot more flexibility than what the `term` crate provided, so it was dropped. We instead switch to writing ANSI escape sequences directly and ignore the TERMINFO database. In addition to fixing several bugs, this commit also permits end users to customize colors to a certain extent. For example, this command will set the match color to magenta and the line number background to yellow: rg --colors 'match:fg:magenta' --colors 'line:bg:yellow' foo For tty handling, we've adopted a hack from `git` to do tty detection in MSYS/mintty terminals. As a result, ripgrep should get both color detection and piping correct on Windows regardless of which terminal you use. Finally, switch to line buffering. Performance doesn't seem to be impacted and it's an otherwise more user friendly option. Fixes #37, Fixes #51, Fixes #94, Fixes #117, Fixes #182, Fixes #231
2016-11-20 18:14:52 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[metadata]
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum aho-corasick 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)" = "d6531d44de723825aa81398a6415283229725a00fa30713812ab9323faa82fc4"
deps: update clap, atty, libc Nothing to see here. Note that we continue to refrain to update tempdir, which means we are still bringing in rand 0.4 and rand 0.3. Updating tempdir brings in an old version of remove_dir_all, which in turn brings in winapi 0.2. No thanks.
2018-03-14 04:36:02 +02:00
"checksum ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"checksum atty 0.2.10 (registry+https://github.com/rust-lang/crates.io-index)" = "2fc4a1aa4c24c0718a250f0681885c1af91419d242f29eb8f2ab28502d80dbd1"
"checksum bitflags 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d0c54bb8f454c567f21197eefcdbf5679d0bd99f2ddbe52e84c77061952e6789"
deps: update bytecount This improves performance with current nightly rustc.
2018-01-30 23:34:30 +02:00
"checksum bytecount 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "882585cd7ec84e902472df34a5e01891202db3bf62614e1f0afe459c1afcf744"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"checksum cfg-if 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "405216fd8fe65f718daa7102ea808a946b6ce40c742998fbfd3463645552de18"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"checksum clap 2.31.2 (registry+https://github.com/rust-lang/crates.io-index)" = "f0f16b89cbb9ee36d87483dc939fe9f1e13c05898d56d7b230a0d4dff033a536"
Update crossbeam to 0.3.2
2018-01-06 14:29:53 +02:00
"checksum crossbeam 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "24ce9782d4d5c53674646a6a4c1863a21a8fc0cb649b3c94dfc16e45071dea19"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"checksum encoding_rs 0.7.2 (registry+https://github.com/rust-lang/crates.io-index)" = "98fd0f24d1fb71a4a6b9330c8ca04cbd4e7cc5d846b54ca74ff376bc7c9f798d"
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"checksum fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
"checksum fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
"checksum glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "8be18de09a56b60ed0edf84bc9df007e30040691af7acd1c41874faac5895bfb"
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c8f31047daa365f19be14b47c29df4f7c3b581832407daabe6ae77397619237d"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"checksum libc 0.2.40 (registry+https://github.com/rust-lang/crates.io-index)" = "6fd41f331ac7c5b8ac259b8bf82c75c0fb2e469bbf37d2becbba9a6a2221965b"
logger: drop env_logger This commit updates the `log` crate to 0.4 and drops the dependency on env_logger. In particular, the latest version of env_logger brings in additional non-optional dependencies such as chrono that I don't think is worth including into ripgrep. It turns out ripgrep doesn't need any fancy logging. We just need a concept of log levels and the ability to print to stderr. Therefore, we just roll our own super simple logger. This update is motivated by the persistent configuration task. In particular, we need the ability to toggle the global log level more than once, and this doesn't appear to be possible with older versions of the log crate.
2018-02-04 04:31:28 +02:00
"checksum log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "89f010e843f2b1a31dbd316b3b8d443758bc634bed37aabade59c686d644e0a2"
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "796fba70e76612589ed2ce7f45282f5af869e0fdd7cc6199fa1aa1f1d591ba9d"
deps: bump memmap to 0.6.2 This removes the last dependency that required winapi 0.2. ripgrep now only depends on winapi 0.3.
2018-01-30 00:09:01 +02:00
"checksum memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e2ffa2c986de11a9df78620c01eeaaf27d94d3ff02bf81bfcca953102dd0c6ff"
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c51a3322e4bca9d212ad9a158a02abc6934d005490c054a2778df73a70aa0a30"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"checksum rand 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "eba5f8cb59cc50ed56be8880a5c7b496bfd9bd26394e176bc67884094145c2c5"
"checksum redox_syscall 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)" = "0d92eecebad22b767915e4d529f89f28ee96dbbf5a4810d2b844373f136417fd"
deps: update everything
2017-10-22 01:42:34 +02:00
"checksum redox_termios 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7e891cfe48e9100a70a3b6eb652fef28920c117d366339687bd5576160db0f76"
deps: update to regex 1.0.1 This causes SIMD to kick in automatically when compiling with stable Rust 1.27+. We also update the README to describe the current state of things. Thanks to @hartley for pointing this out: https://twitter.com/hartley/status/1009950392862453760
2018-06-22 02:10:53 +02:00
"checksum regex 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "13c93d55961981ba9226a213b385216f83ab43bd6ac53ab16b2eeb47e337cf4e"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"checksum regex-syntax 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "8f1ac0f60d675cc6cf13a20ec076568254472551051ad5dd050364d70671bf6b"
deps: update remove_dir_all
2018-04-21 18:13:16 +02:00
"checksum remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3488ba1b9a2084d38645c4c08276a1752dcbf2c7130d74f1569681ad5d2799c5"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"checksum same-file 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "cfb6eded0b06a0b512c8ddbcf04089138c9b4362c2f696f3c3d76039d68f3637"
deps: update regex to 1.0 We retain the `simd-accel` feature on globset for backwards compatibility, but will remove it in the next semver release.
2018-05-07 19:07:30 +02:00
"checksum simd 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "ed3686dd9418ebcc3a26a0c0ae56deab0681e53fe899af91f5bbcee667ebffb1"
argv: update clap to 2.29.4 We use the new AppSettings::AllArgsOverrideSelf to permit all flags to be specified multiple times. This removes the need for our previous work-around where we would enable `multiple` for every flag and then just extract the last value when consuming clap's matches. We also add a couple regression tests that ensure repeated switches and flags work as expected.
2018-02-06 02:22:44 +02:00
"checksum strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bb4f380125926a99e52bc279241539c018323fab05ad6368b56f93d9369ff550"
deps: update all dependencies In particular, we can now drop rand 0.3.
2018-04-01 16:59:44 +02:00
"checksum tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)" = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
deps: update everything
2017-10-22 01:42:34 +02:00
"checksum termion 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "689a3bdfaab439fd92bc87df5c4c78417d3cbe537487274e9b0b2dce76e92096"
deps: update to latest clap release This also bumps the minimum Rust version required to 1.20.
2017-12-30 22:47:19 +02:00
"checksum textwrap 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c0b59b6b4b44d867f1370ef1bd91bfb262bf07bf0ae65c202ea2fbc16153b693"
deps: update all deps
2017-12-30 22:48:25 +02:00
"checksum thread_local 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "279ef31c19ededf577bfd12dfae728040a21f635b06a24cd670ff510edd38963"
deps: update regex crate This update brings with it a new feature of the regex crate which will now use SIMD optimizations automatically at runtime with no necessary compile time flags. All that's needed is to enable the `unstable` feature. Other crates, such as bytecount and encoding_rs, are still using the old-style SIMD support, so we leave the simd-accel and avx-accel features. However, the binaries we distribute on Github no longer have those features enabled, which makes them truly portable. Fixes #135
2018-03-10 21:02:06 +02:00
"checksum ucd-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "fd2be2d6639d0f8fe6cdda291ad456e23629558d466e2789d2c3e9892bda285d"
update deps
2016-12-24 15:32:32 +02:00
"checksum unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "bf3a113775714a22dcb774d8ea3655c53a32debae63a063acc00a91cc586245f"
bump deps
2017-08-24 01:52:13 +02:00
"checksum unreachable 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "382810877fe448991dfc7f0dd6e3ae5d58088fd0ea5e35189655f84e6814fa56"
Update to regex 0.2.
2016-12-30 23:24:09 +02:00
"checksum utf8-ranges 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "662fab6525a98beff2921d7f61a39e7d59e0b425ebc7d0d9e66d316e55124122"
update deps
2016-10-30 04:27:29 +02:00
"checksum void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
ignore: fix performance regression on Windows This commit fixes a performance regression in Windows that resulted from fallout from fixing #705. In particular, we introduced an additional stat call for every single directory entry, which can be quite disastrous for performance. There is a corresponding companion PR that fixes the same bug in walkdir: https://github.com/BurntSushi/walkdir/pull/96 Fixes #820
2018-02-21 02:32:58 +02:00
"checksum walkdir 2.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "63636bd0eb3d00ccb8b9036381b526efac53caf112b7783b730ab3f8e44da369"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
"checksum winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "04e3bd221fcbe8a271359c04f21a76db7d0c6028862d1bb5512d85e1e2eb5bb3"
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Reference in New Issue Copy Permalink