rust/ripgrep
1
0
Fork 0
mirror of https://github.com/BurntSushi/ripgrep.git synced 2024-12-12 19:18:24 +02:00
Code Issues Releases Activity
332ad18401
ripgrep/Cargo.lock

787 lines
33 KiB
Plaintext
Raw Normal View History

cargo: include auto-generated message This is going to be annoying for a while if one switches between the latest nightly compiler and older compilers. Sigh.
2019-01-29 20:04:40 +02:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "aho-corasick"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.6.9"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +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 atty and winapi This updates atty and winapi to their latest versions, including the bug fix in atty that allows it to work with winapi 0.3.5.
2018-07-22 19:07:48 +02:00
version = "0.2.11"
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 other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.6 (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 various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
[[package]]
name = "autocfg"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "base64"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.10.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"byteorder 1.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +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: various patch upgrades
2018-08-22 04:00:31 +02:00
version = "1.0.4"
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 to bytecount 0.5 bytecount now uses runtime dispatch for enabling SIMD, which means we can no longer need the avx-accel features. We remove it from ripgrep since the next release will be a minor version bump, but leave them as no-ops for the crates that previously used it.
2019-01-19 16:52:10 +02:00
version = "0.5.0"
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"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "byteorder"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "1.3.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "cc"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "1.0.28"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +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 = "cfg-if"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.1.6"
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 transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
version = "2.32.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"
dependencies = [
deps: various patch upgrades
2018-08-22 04:00:31 +02:00
"bitflags 1.0.4 (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 all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"textwrap 0.10.0 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-width 0.1.5 (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]]
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: various patch upgrades
2018-08-22 04:00:31 +02:00
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
]
[[package]]
name = "crossbeam-channel"
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
version = "0.3.8"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"smallvec 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
]
[[package]]
name = "crossbeam-utils"
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
version = "0.6.5"
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"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
"lazy_static 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +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
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: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
version = "0.8.16"
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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
"packed_simd 0.3.3 (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
]
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
[[package]]
name = "encoding_rs_io"
searcher: always strip BOM This fixes a bug where a BOM prefix was included. While this was somewhat intentional in order to have a faithful "UTF8 passthru" option, in practice, this causes problems such as breaking patterns like `^` in a really non-obvious way. The actual fix was to add a new API to encoding_rs_io, which this commit brings in. Fixes #1163
2019-01-26 00:18:57 +02:00
version = "0.1.4"
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
"encoding_rs 0.8.16 (registry+https://github.com/rust-lang/crates.io-index)",
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +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]]
deps: update other deps
2019-01-29 20:08:56 +02:00
name = "fuchsia-cprng"
version = "0.1.0"
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"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.4.2"
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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"aho-corasick 0.6.9 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update all deps
2017-12-30 22:48:25 +02:00
"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)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (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"
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
version = "0.2.3"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-cli 0.1.1",
"grep-matcher 0.1.1",
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
"grep-pcre2 0.1.2",
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-printer 0.1.1",
"grep-regex 0.1.1",
grep-searcher-0.1.2
2019-02-09 23:12:16 +02:00
"grep-searcher 0.1.2",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"termcolor 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"walkdir 2.2.7 (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
]
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
[[package]]
name = "grep-cli"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.1.1"
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
dependencies = [
"atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"globset 0.4.2",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"lazy_static 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"same-file 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"termcolor 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"winapi-util 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "grep-matcher"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.1.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-pcre2"
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
version = "0.1.2"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-matcher 0.1.1",
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
"pcre2 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-printer"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.1.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-matcher 0.1.1",
"grep-regex 0.1.1",
grep-searcher-0.1.2
2019-02-09 23:12:16 +02:00
"grep-searcher 0.1.2",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"serde 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"serde_json 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"termcolor 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-regex"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.1.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-matcher 0.1.1",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: bump regex-syntax to 0.6.5 This is necessary for the use of the new is_line_anchored_{start,end} APIs.
2019-01-26 19:20:02 +02:00
"regex-syntax 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"utf8-ranges 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-searcher"
grep-searcher-0.1.2
2019-02-09 23:12:16 +02:00
version = "0.1.2"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: update to bytecount 0.5 bytecount now uses runtime dispatch for enabling SIMD, which means we can no longer need the avx-accel features. We remove it from ripgrep since the next release will be a minor version bump, but leave them as no-ops for the crates that previously used it.
2019-01-19 16:52:10 +02:00
"bytecount 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
"encoding_rs 0.8.16 (registry+https://github.com/rust-lang/crates.io-index)",
searcher: always strip BOM This fixes a bug where a BOM prefix was included. While this was somewhat intentional in order to have a faithful "UTF8 passthru" option, in practice, this causes problems such as breaking patterns like `^` in a really non-obvious way. The actual fix was to add a new API to encoding_rs_io, which this commit brings in. Fixes #1163
2019-01-26 00:18:57 +02:00
"encoding_rs_io 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"grep-matcher 0.1.1",
"grep-regex 0.1.1",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update memmap
2019-01-19 16:55:24 +02:00
"memmap 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
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-0.4.6
2018-12-30 15:46:09 +02:00
version = "0.4.6"
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 = [
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
"crossbeam-channel 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
"globset 0.4.2",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"lazy_static 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"same-file 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"tempfile 3.0.5 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"walkdir 2.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"winapi-util 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "itoa"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.4.3"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "lazy_static"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "1.2.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 other deps
2019-01-29 20:08:56 +02:00
version = "0.2.48"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "log"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.4.6"
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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"cfg-if 0.1.6 (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 various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "2.1.3"
bump various versions
2016-12-30 22:43:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (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: update memmap
2019-01-19 16:55:24 +02:00
version = "0.7.0"
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 other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.6 (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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "1.9.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 other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (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
]
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
[[package]]
name = "packed_simd"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "pcre2"
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
version = "0.1.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
"pcre2-sys 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pcre2-sys"
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
version = "0.1.1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"cc 1.0.28 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other crates
2018-08-31 05:03:07 +02:00
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "pkg-config"
deps: update other crates
2018-08-31 05:03:07 +02:00
version = "0.3.14"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "proc-macro2"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.4.26"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "quote"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.6.11"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"proc-macro2 0.4.26 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
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"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.6.5"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_jitter 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_os 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"rand_pcg 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.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
]
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
[[package]]
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
name = "rand_chacha"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "0.1.1"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
]
[[package]]
name = "rand_core"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.4.0"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "rand_hc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
]
[[package]]
name = "rand_isaac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
]
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
[[package]]
deps: update other deps
2019-01-29 20:08:56 +02:00
name = "rand_jitter"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update other deps
2019-01-29 20:08:56 +02:00
dependencies = [
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_os"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
dependencies = [
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"fuchsia-cprng 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
[[package]]
name = "rand_pcg"
version = "0.1.1"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_xorshift"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
]
[[package]]
name = "rdrand"
version = "0.4.0"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
]
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
deps: update everything
2017-10-22 01:42:34 +02:00
[[package]]
name = "redox_syscall"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.1.51"
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 other deps
2019-01-29 20:08:56 +02:00
"redox_syscall 0.1.51 (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 regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
version = "1.1.0"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"aho-corasick 0.6.9 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
deps: bump regex-syntax to 0.6.5 This is necessary for the use of the new is_line_anchored_{start,end} APIs.
2019-01-26 19:20:02 +02:00
"regex-syntax 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"utf8-ranges 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 = "regex-syntax"
deps: bump regex-syntax to 0.6.5 This is necessary for the use of the new is_line_anchored_{start,end} APIs.
2019-01-26 19:20:02 +02:00
version = "0.6.5"
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 = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.6 (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
]
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"
deps: update versions for all crates I don't think every change here is needed, but this ensures we're using the latest version of every direct dependency.
2018-09-07 19:14:31 +02:00
version = "0.10.0"
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 all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"clap 2.32.0 (registry+https://github.com/rust-lang/crates.io-index)",
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
"grep 0.2.3",
ignore-0.4.6
2018-12-30 15:46:09 +02:00
"ignore 0.4.6",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"lazy_static 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
"num_cpus 1.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"serde 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"serde_json 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"termcolor 1.0.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
]
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
[[package]]
name = "ryu"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.2.7"
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
source = "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
[[package]]
name = "same-file"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "1.0.4"
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 = [
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"winapi-util 0.1.2 (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
]
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "serde"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "1.0.85"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "serde_derive"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "1.0.85"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"proc-macro2 0.4.26 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"syn 0.15.26 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "serde_json"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "1.0.37"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"itoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"ryu 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"serde 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
[[package]]
name = "smallvec"
deps: update other deps
2019-01-29 20:08:56 +02:00
version = "0.6.8"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unreachable 1.0.0 (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"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "syn"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
version = "0.15.26"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update other deps
2019-01-29 20:08:56 +02:00
"proc-macro2 0.4.26 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
name = "tempfile"
version = "3.0.5"
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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.51 (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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.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
]
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"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "1.0.4"
deps: update termcolor to 1.0.0
2018-07-18 00:37:02 +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
dependencies = [
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
"wincolor 1.0.1 (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
]
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 other deps
2019-01-29 20:08:56 +02:00
"libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.51 (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 all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
version = "0.10.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 = [
deps: update all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
]
update deps
2016-10-30 04:27:29 +02:00
[[package]]
name = "thread_local"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
version = "0.3.6"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"lazy_static 1.2.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"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.1.3"
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"
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"
deps: update all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
version = "0.1.5"
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]]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
name = "unicode-xid"
version = "0.1.0"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
[[package]]
name = "unreachable"
version = "1.0.0"
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"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "1.0.2"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +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"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "2.2.7"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"same-file 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"winapi-util 0.1.2 (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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
version = "0.3.6"
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"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
[[package]]
name = "winapi-util"
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
version = "0.1.2"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[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"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
version = "1.0.1"
deps: update termcolor to 1.0.0
2018-07-18 00:37:02 +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
dependencies = [
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"winapi-util 0.1.2 (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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum aho-corasick 0.6.9 (registry+https://github.com/rust-lang/crates.io-index)" = "1e9a933f4e58658d7b12defcf96dc5c720f20832deebe3e0a19efd3b6aaeeb9e"
deps: update atty and winapi This updates atty and winapi to their latest versions, including the bug fix in atty that allows it to work with winapi 0.3.5.
2018-07-22 19:07:48 +02:00
"checksum atty 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "9a7d5b8723950951411ee34d271d99dddcc2035a16ab25310ea2c8cfd4369652"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum autocfg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a6d640bee2da49f60a4068a7fae53acde8982514ab7bae8b8cea9e88cbcfd799"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
deps: various patch upgrades
2018-08-22 04:00:31 +02:00
"checksum bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "228047a76f468627ca71776ecdebd732a3423081fcf5125585bcd7c49886ce12"
deps: update to bytecount 0.5 bytecount now uses runtime dispatch for enabling SIMD, which means we can no longer need the avx-accel features. We remove it from ripgrep since the next release will be a minor version bump, but leave them as no-ops for the crates that previously used it.
2019-01-19 16:52:10 +02:00
"checksum bytecount 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c219c0335c21a8bd79587ce5aee9f64aff1d0bd7a2cca7a58a815f9780cd3b0d"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum byteorder 1.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a019b10a2a7cdeb292db131fc8113e57ea2a908f6e7894b0c3c671893b65dbeb"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum cc 1.0.28 (registry+https://github.com/rust-lang/crates.io-index)" = "bb4a8b715cb4597106ea87c7c84b2f1d452c7492033765df7f32651e66fcf749"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "082bb9b28e00d3c9d39cc03e64ce4cea0f1bb9b3fde493f0cbc008472d22bdf4"
deps: update all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"checksum clap 2.32.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b957d88f4b6a63b9d70d5f454ac8011819c6efa7727858f458ab71c756ce2d3e"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
"checksum cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
deps: update to crossbeam-channel 0.3.8 This drops dependencies on parking_lot and rand from ripgrep. (rand is still used for tests.)
2019-01-29 20:07:37 +02:00
"checksum crossbeam-channel 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "0f0ed1a4de2235cabda8558ff5840bffb97fcb64c97827f354a451307df5f72b"
"checksum crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "f8306fcef4a7b563b76b7dd949ca48f52bc1141aa067d2ea09565f3e2652aa5c"
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
"checksum encoding_rs 0.8.16 (registry+https://github.com/rust-lang/crates.io-index)" = "0535f350c60aac0b87ccf28319abc749391e912192255b0c00a2c12c6917bd73"
searcher: always strip BOM This fixes a bug where a BOM prefix was included. While this was somewhat intentional in order to have a faithful "UTF8 passthru" option, in practice, this causes problems such as breaking patterns like `^` in a really non-obvious way. The actual fix was to add a new API to encoding_rs_io, which this commit brings in. Fixes #1163
2019-01-26 00:18:57 +02:00
"checksum encoding_rs_io 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "6c89a56158243c7cde22fde70e452a40dded9d9d9100f71273df19af9be4d034"
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 other deps
2019-01-29 20:08:56 +02:00
"checksum fuchsia-cprng 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "81f7f8eb465745ea9b02e2704612a9946a59fa40572086c6fd49d6ddcf30bf31"
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 most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum itoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "1306f3464951f30e30d12373d31c79fbd52d236e5e896fd92f96ec7babbbe60b"
"checksum lazy_static 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a374c89b9db55895453a74c1e38861d9deec0b01b405a82516e9d5de4820dea1"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum libc 0.2.48 (registry+https://github.com/rust-lang/crates.io-index)" = "e962c7641008ac010fa60a7dfdc1712449f29c44ef2d4702394aea943ee75047"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum log 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c84ec4b527950aa83a329754b01dbe3f58361d1c5efacd1f6d68c494d08a17c6"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum memchr 2.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "e1dd4eaac298c32ce07eb6ed9242eda7d82955b9170b7d6db59b2e02cc63fcb8"
deps: update memmap
2019-01-19 16:55:24 +02:00
"checksum memmap 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6585fd95e7bb50d6cc31e20d4cf9afb4e2ba16c5846fc76793f11218da9c475b"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum num_cpus 1.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5a69d464bdc213aaaff628444e99578ede64e9c854025aa43b9796530afa9238"
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
"checksum packed_simd 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "a85ea9fc0d4ac0deb6fe7911d38786b32fc11119afd9e9d38b84ff691ce64220"
pcre2: use jit_if_available This will allow PCRE2 to fall back to non-JIT matching when running on platforms without JIT support. ref https://github.com/BurntSushi/rust-pcre2/issues/3
2018-09-08 23:12:14 +02:00
"checksum pcre2 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3ae0a2682105ec5ca0ee5910bbc7e926386d348a05166348f74007942983c319"
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
"checksum pcre2-sys 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a9027f9474e4e13d3b965538aafcaebe48c803488ad76b3c97ef061a8324695f"
deps: update other crates
2018-08-31 05:03:07 +02:00
"checksum pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)" = "676e8eb2b1b4c9043511a9b7bea0915320d7e502b0a079fb03f9635a5252b18c"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum proc-macro2 0.4.26 (registry+https://github.com/rust-lang/crates.io-index)" = "38fddd23d98b2144d197c0eca5705632d4fe2667d14a6be5df8934f8d74f1978"
"checksum quote 0.6.11 (registry+https://github.com/rust-lang/crates.io-index)" = "cdd8e04bd9c52e0342b406469d494fcb033be4bdbe5c606016defbb1681411e1"
"checksum rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "6d71dacdc3c88c1fde3885a3be3fbab9f35724e6ce99467f7d9c5026132184ca"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
"checksum rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d0e7a549d590831370895ab7ba4ea0c1b6b011d106b5ff2da6eee112615e6dc0"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"checksum rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
"checksum rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum rand_jitter 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "29fe7b8bc348249f3b1bbb9ab8baa6fa3419196ecfbf213408bca1b2494710de"
"checksum rand_os 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "b7c690732391ae0abafced5015ffb53656abfaec61b342290e5eb56b286a679d"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"checksum rand_pcg 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "086bd09a33c7044e56bb44d5bdde5a60e7f119a9e95b0775f545de759a32fe05"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
"checksum rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum redox_syscall 0.1.51 (registry+https://github.com/rust-lang/crates.io-index)" = "423e376fffca3dfa06c9e9790a9ccd282fafb3cc6e6397d01dbf64f9bacc6b85"
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 regex and regex-syntax This brings in some new Unicode properties, such as \p{Emoji}. It is now also technically possible construct a regex that recognizes grapheme clusters.
2018-12-09 23:33:37 +02:00
"checksum regex 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "37e7cbbd370869ce2e8dff25c7018702d10b21a20ef7135316f8daecd6c25b7f"
deps: bump regex-syntax to 0.6.5 This is necessary for the use of the new is_line_anchored_{start,end} APIs.
2019-01-26 19:20:02 +02:00
"checksum regex-syntax 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "8c2f35eedad5295fdf00a63d7d4b238135723f92b434ec06774dad15c7ab0861"
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 to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"checksum rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum ryu 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "eb9e9b8cde282a9fe6a42dd4681319bfb63f121b8a8ee9439c6f4107e58a46f7"
"checksum same-file 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "8f20c4be53a8a1ff4c1f1b2bd14570d2f634628709752f0702ecdd2b3f9a5267"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"checksum semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
"checksum semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
deps: update various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum serde 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)" = "534b8b91a95e0f71bca3ed5824752d558da048d4248c91af873b63bd60519752"
"checksum serde_derive 1.0.85 (registry+https://github.com/rust-lang/crates.io-index)" = "a915306b0f1ac5607797697148c223bedeaa36bcc2e28a01441cd638cc6567b4"
deps: update other deps
2019-01-29 20:08:56 +02:00
"checksum serde_json 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)" = "4b90a9fbe1211e57d3e1c15670f1cb00802988fb23a1a4aad7a2b63544f1920e"
"checksum smallvec 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)" = "88aea073965ab29f6edb5493faf96ad662fb18aa9eeb186a3b7057951605ed15"
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 various dependencies We also increase the MSRV to 1.32, the current stable release, which sets the stage for migrating to Rust 2018.
2019-01-19 16:32:32 +02:00
"checksum syn 0.15.26 (registry+https://github.com/rust-lang/crates.io-index)" = "f92e629aa1d9c827b2bb8297046c1ccffc57c99b947a680d3ccff1f136a3bee9"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
"checksum tempfile 3.0.5 (registry+https://github.com/rust-lang/crates.io-index)" = "7e91405c14320e5c79b3d148e1c86f40749a36e490642202a31689cb1a3452b2"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum termcolor 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "4096add70612622289f2fdcdbd5086dc81c1e2675e6ae58d6c4f62a16c6d7f2f"
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 all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"checksum textwrap 0.10.0 (registry+https://github.com/rust-lang/crates.io-index)" = "307686869c93e71f94da64286f9a9524c0f308a9e1c87a583de8e9c9039ad3f6"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"checksum thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "535c204ee4d8434478593480b8f86ab45ec9aae0e83c568ca81abf0fd0e88f86"
deps: update all transitive dependencies This updates all remaining transitive dependencies. Most changes appear minor and there appear to be no minimum Rust version conflicts. Yay!
2018-07-18 02:34:03 +02:00
"checksum unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "882386231c45df4700b275c7ff55b6f3698780a650026380e72dabe76fa46526"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
"checksum unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fc72304796d0818e357ead4e000d19c9c174ab23dc11093ac919054d20a6a7fc"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
"checksum unreachable 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "382810877fe448991dfc7f0dd6e3ae5d58088fd0ea5e35189655f84e6814fa56"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum utf8-ranges 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "796f7e48bef87609f7ade7e06495a87d5cd06c7866e6a5cbfceffc558a243737"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
"checksum void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
deps: update most other dependencies This commit is the result of doing: $ cargo update $ cargo update -p encoding_rs --precise 0.8.10 where the latter line prevents encoding_rs from updating to 0.8.11 (or newer). In particular, the 0.8.11 release increased the minimum Rust version to 1.29, where as ripgrep 0.10.x is still on 1.28. We stay on an older version for now until ripgrep is ready to move to 0.11.x.
2018-12-15 15:42:14 +02:00
"checksum walkdir 2.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "9d9d7ed3431229a144296213105a390676cc49c9b6a72bd19f3176c98e129fa1"
"checksum winapi 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "92c1eb33641e276cfa214a0522acad57be5c56b10cb348b3c5117db75f3ac4b0"
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-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
ignore: correctly detect hidden files on Windows This commit fixes a bug where ripgrep only treated files beginning with a `.` as hidden. On Windows, we continue this tradition, but additionally check whether a file has the special Windows "hidden" attribute set. If so, we treat it as a hidden file. In order to make this work without an additional stat call, we had to rearrange some of the plumbing from the directory traverser. Fixes #1154
2019-01-27 17:45:09 +02:00
"checksum winapi-util 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7168bab6e1daee33b4557efd0e95d5ca70a03706d39fa5f3fe7a236f584b03c9"
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-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
"checksum wincolor 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "561ed901ae465d6185fa7864d63fbd5720d0ef718366c9a4dc83cf6170d7e9ba"
Reference in New Issue Copy Permalink