No description
Find a file
bors[bot] 582ea0a29a Merge #383
383: Bump failure from 0.1.3 to 0.1.4 r=DJMcNab a=dependabot[bot]

Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.3 to 0.1.4.
<details>
<summary>Changelog</summary>

*Sourced from [failure's changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md).*

> # Version 0.1.4
> 
> - Improved error reporting of the derive feature
> - Resolved a potential internal ambiguity when using the backtrace feature
>   that prevented backtrace from improving an upstream API.
> - Changed the bounds on std error compat conversions through the From trait
>   to take Sync and Send into account.
</details>
<details>
<summary>Commits</summary>

- [`70b98e6`](70b98e653a) 0.1.4
- [`937fb70`](937fb704a4) Add Sync and Send as failure::Error supports them. ([#283](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/283))
- [`15b6798`](15b6798695) Improving procmacro error reporting
- [`22bfd31`](22bfd319a6) support trailing commas in macros ([#273](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/273))
- [`26fc6eb`](26fc6eb713) Future proof debug formatting.  Fixes [#279](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/279)
- [`0f89723`](0f89723f1e) Reformat for latest rustfmt
- [`8f8f92f`](8f8f92fa55) Update metadata to point to new docs
- See full diff in [compare view](https://github.com/rust-lang-nursery/failure/compare/0.1.3...0.1.4)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=failure&package-manager=cargo&previous-version=0.1.3&new-version=0.1.4)](https://dependabot.com/compatibility-score.html?dependency-name=failure&package-manager=cargo&previous-version=0.1.3&new-version=0.1.4)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>

Co-authored-by: dependabot[bot] <support@dependabot.com>
2018-12-31 09:41:32 +00:00
.cargo Reimplement format-hook using a rust binary 2018-12-09 12:27:13 +00:00
crates Bump failure from 0.1.3 to 0.1.4 2018-12-31 08:53:49 +00:00
editors Document formatting capabilities 2018-12-29 21:57:46 +01:00
.gitignore Ignore intellij files 2018-12-29 20:09:36 +01:00
.travis.yml Disable incremental compilation again on CI 2018-12-30 20:48:35 +00:00
ARCHITECTURE.md fix typos 2018-12-20 14:34:16 +01:00
bors.toml don't gate on appveyor 2018-10-09 19:06:05 +03:00
Cargo.lock Bump failure from 0.1.3 to 0.1.4 2018-12-31 08:53:49 +00:00
Cargo.toml fix the cancellation bug 2018-12-30 11:09:17 +03:00
CONTRIBUTING.md brush up docs 2018-10-15 01:05:18 +03:00
LICENSE-APACHE Licenses 2018-01-10 22:47:04 +03:00
LICENSE-MIT Licenses 2018-01-10 22:47:04 +03:00
README.md update README with Rust 1.31 2018-12-28 14:02:23 -08:00
ROADMAP.md don't mention beta channel Rust in ROADMAP 2018-12-28 14:38:27 -08:00
rustfmt.toml Don't order import alphabetical 2018-11-01 16:18:53 +03:00

Rust Analyzer

Build Status

Rust Analyzer is an experimental modular compiler frontend for the Rust language, which aims to lay a foundation for excellent IDE support.

It doesn't implement much of compiler functionality yet, but the white-space preserving Rust parser works, and there are significant chunks of overall architecture (indexing, on-demand & lazy computation, snapshotable world view) in place. Some basic IDE functionality is provided via a language server.

Work on the Rust Analyzer is sponsored by

Ferrous Systems

Quick Start

Rust analyzer builds on Rust >= 1.31.0 and uses the 2018 edition.

# run tests
$ cargo test

# show syntax tree of a Rust file
$ cargo run --package ra_cli parse < crates/ra_syntax/src/lib.rs

# show symbols of a Rust file
$ cargo run --package ra_cli symbols < crates/ra_syntax/src/lib.rs

To try out the language server, see these instructions. Please note that the server is not ready for general use yet. If you are looking for a Rust IDE that works, use IntelliJ Rust or RLS. That being said, the basic stuff works, and rust analyzer is developed in the rust analyzer powered editor.

Current Status and Plans

Rust analyzer aims to fill the same niche as the official Rust Language Server, but uses a significantly different architecture. More details can be found in this thread, but the core issue is that RLS works in the "wait until user stops typing, run the build process, save the results of the analysis" mode, which arguably is the wrong foundation for IDE.

Rust Analyzer is a hobby project at the moment, there's exactly zero guarantees that it becomes production-ready one day.

The near/mid term plan is to work independently of the main rustc compiler and implement at least simplistic versions of name resolution, macro expansion and type inference. The purpose is two fold:

  • to quickly bootstrap usable and useful language server: solution that covers 80% of Rust code will be useful for IDEs, and will be vastly simpler than 100% solution.

  • to understand how the consumer-side of compiler API should look like (especially it's on-demand aspects). If you have get_expression_type function, you can write a ton of purely-IDE features on top of it, even if the function is only partially correct. Plugin in the precise function afterwards should just make IDE features more reliable.

The long term plan is to merge with the mainline rustc compiler, probably around the HIR boundary? That is, use rust analyzer for parsing, macro expansion and related bits of name resolution, but leave the rest (including type inference and trait selection) to the existing rustc.

Getting in touch

We have a Discord server dedicated to compilers and language servers implemented in Rust: https://discord.gg/sx3RQZB.

Contributing

See CONTRIBUTING.md and ARCHITECTURE.md

License

Rust analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.