diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-01-22 18:09:58 -0500 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-01-22 18:09:58 -0500 |
| commit | 4db64bd82426fd914f98059e3fb7a146ed57ad9c (patch) | |
| tree | ad1ef659671f2f6385cf3bf5c0d49480e927cf1b /src/rustllvm/RustWrapper.cpp | |
| parent | c76ce8c36cf39ee8036401a95c583dda8f0f38d6 (diff) | |
| parent | 3819c222a84a9c21992b81939420643c0a969e7d (diff) | |
| download | rust-4db64bd82426fd914f98059e3fb7a146ed57ad9c.tar.gz rust-4db64bd82426fd914f98059e3fb7a146ed57ad9c.zip | |
Rollup merge of #21217 - Gankro:docadoca, r=steveklabnik
Not sure on what *exactly* should be said here, but I think this is the most important bit. This PR also establishes conventions for describing performance minimally. I suggest to describe preformance for individual methods we use a `# Performance` heading. Not sure if we should have ``` # Performance: O(1) details details ``` or ``` # Performance: O(1) details details ``` Since I think most methods don't need discussion, the former seems more resonable. But it's kind of weird to have info "in" the heading. r? @steveklabnik
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions