9d7b130041
For the benefit of the pretty printer we want to keep track of how string literals in the ast were originally represented in the source code. This commit changes parser functions so they don't extract strings from the token stream without at least also returning what style of string literal it was. This is stored in the resulting ast node for string literals, obviously, for the package id in `extern mod = r"package id"` view items, for the inline asm in `asm!()` invocations. For `asm!()`'s other arguments or for `extern "Rust" fn()` items, I just the style of string, because it seemed disproportionally cumbersome to thread that information through the string processing that happens with those string literals, given the limited advantage raw string literals would provide in these positions. The other syntax extensions don't seem to store passed string literals in the ast, so they also discard the style of strings they parse. |
||
|---|---|---|
| .. | ||
| testsuite | ||
| api.rs | ||
| conditions.rs | ||
| context.rs | ||
| crate.rs | ||
| exit_codes.rs | ||
| installed_packages.rs | ||
| messages.rs | ||
| package_id.rs | ||
| package_source.rs | ||
| path_util.rs | ||
| README.txt | ||
| rustpkg.rs | ||
| search.rs | ||
| source_control.rs | ||
| target.rs | ||
| tests.rs | ||
| usage.rs | ||
| util.rs | ||
| version.rs | ||
| workcache_support.rs | ||
| workspace.rs | ||
Right now, commands that work are "build" and "clean".
`rustpkg build` and `rustpkg clean` should work
for example:
$ cd ~/rust/src/librustpkg/testsuite/pass
$ rustpkg build hello-world
... some output ...
$ rustpkg clean hello-world
-------------
the following test packages in librustpkg/testsuite/pass:
* hello-world
* install-paths
* simple-lib
* deeply/nested/path
* fancy-lib
It fails on the following test packages:
* external-crate (no support for `extern mod` inference yet)
and should fail with proper error messages
on all of the test packages in librustpkg/testsuite/fail
* no-inferred-crates