about summary refs log tree commit diff
path: root/src/test/ui/codemap_tests
AgeCommit message (Collapse)AuthorLines
2018-02-26Update UI testsVadim Petrochenkov-42/+42
2018-02-25Update ui testsGuillaume Gomez-0/+13
2017-12-19Point at `while true` span instead of entire blockEsteban Küber-3/+1
2017-12-11Auto merge of #46608 - estebank:resolve-return, r=nikomatsakisbors-1/+1
Resolve type on return type suggestion Partially address #45871.
2017-12-10Update ui tests' line numbers.Tommy Ip-2/+2
2017-12-10Add must-compile-successfully comment to appropriate ui tests.Tommy Ip-0/+2
2017-12-09Resolve type on return type suggestionEsteban Küber-1/+1
2017-12-06Auto merge of #45953 - estebank:tab-4, r=nikomatsakisbors-11/+11
Display `\t` in diagnostics code as four spaces Follow up to #44386 using the unicode variable width machinery from #45711 to replace tabs in the source code when displaying a diagnostic error with four spaces (instead of only one), while properly accounting for this when calculating underlines. Partly addresses #44618.
2017-11-26mention nightly in -Z external-macro-backtrace noteAlex Burka-4/+4
2017-11-24Display `\t` in diagnostics code as four spacesEsteban Küber-11/+11
2017-11-24Merge cfail and ui tests into ui testsOliver Schneider-36/+36
2017-11-20address review commentsAlex Burka-4/+4
2017-11-19use -Z flag instead of env varAlex Burka-4/+4
2017-11-19update UI testsAlex Burka-4/+4
2017-11-03Display spans correctly when there are non-half-width charactersWonwoo Choi-1/+66
2017-09-07Fix mispositioned error indicatorsest31-3/+75
Fixes #38384 Most of the Rust community uses 4 spaces for indentation, but there are also tab users of Rust (including myself!). This patch fixes a bug in error printing which mispositions error indicators when near code with tabs. The code attempted to fix the issue by replacing spaces with tabs, but it sadly wasn't enough, as sometimes you may not print spaces but _ or ^ instead. This patch employs the reverse strategy: it replaces each tab with a space, so that the number of _ and ^ and spaces in error indicators below the code snippet line up perfectly. In a study [1] preceeding this patch, we could see that this strategy is also chosen by gcc version 6.3.0. Its not perfect, as the output is not beautiful, but its the easiest to implement. If anyone wants to improve on this, be my guest! This patch is meant as improvement of the status quo, not as perfect end status. It fixes the actual issue of mispositioning error indicators. [1]: https://github.com/rust-lang/rust/issues/38384#issuecomment-326813710
2017-09-05Print more detailed trait-ref for intercrate ambiguity.Masaki Hara-1/+1
2017-09-05Fix a very subtle mistake in a ui test.Masaki Hara-0/+1
2017-09-05Add tests for intercrate ambiguity hints.Masaki Hara-0/+1
2017-07-02Revert "Change error count messages"Ariel Ben-Yehuda-11/+11
This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-05-27Add invalid unary operator usage error codeGuillaume Gomez-1/+1
2017-05-27Add new error codes and update testsGuillaume Gomez-1/+1
2017-05-26Auto merge of #42058 - froydnj:thiscall-support, r=nikomatsakisbors-1/+1
add thiscall calling convention support This support is needed for bindgen to work well on 32-bit Windows, and also enables people to begin experimenting with C++ FFI support on that platform. Fixes #42044.
2017-05-24add thiscall calling convention supportNathan Froyd-1/+1
This support is needed for bindgen to work well on 32-bit Windows, and also enables people to begin experimenting with C++ FFI support on that platform. Fixes #42044.
2017-05-24Change error count messagesMichael Kohl-11/+11
See #33525 for details.
2017-04-04Move 'coherence-overlapping-inherent-impl-trait' test to uitopecongiro-0/+26
2017-04-04Move 'overlapping_inherent_impls' test to uitopecongiro-0/+75
2017-03-27borrowck: consolidate `mut` suggestionsAriel Ben-Yehuda-1/+1
This converts all of borrowck's `mut` suggestions to a new `mc::ImmutabilityBlame` API instead of the current mix of various hacks. Fixes #35937. Fixes #40823.
2017-03-10fix #40294 obligation cause.body_id is not always a NodeExprCengiz Can-50/+0
2017-03-02Add support for x86-interrupt calling conventionPhilipp Oppermann-1/+1
Tracking issue: https://github.com/rust-lang/rust/issues/40180 This calling convention can be used for definining interrupt handlers on 32-bit and 64-bit x86 targets. The compiler then uses `iret` instead of `ret` for returning and ensures that all registers are restored to their original values. Usage: ``` extern "x86-interrupt" fn handler(stack_frame: &ExceptionStackFrame) {…} ``` for interrupts and exceptions without error code and ``` extern "x86-interrupt" fn page_fault_handler(stack_frame: &ExceptionStackFrame, error_code: u64) {…} ``` for exceptions that push an error code (e.g., page faults or general protection faults). The programmer must ensure that the correct version is used for each interrupt. For more details see the [LLVM PR][1] and the corresponding [proposal][2]. [1]: https://reviews.llvm.org/D15567 [2]: http://lists.llvm.org/pipermail/cfe-dev/2015-September/045171.html
2017-02-04Add a new ui test and update existing onesCengiz Can-14/+38
2017-02-04Remove extra newlines from expectation filesCengiz Can-1/+0
2017-02-04Improve error message for uninferrable types #38812Cengiz Can-2/+5
2017-01-18calling convention for MSP430 interruptsJorge Aparicio-1/+1
This calling convention is used to define interrup handlers on MSP430 microcontrollers. Usage looks like this: ``` rust #[no_mangle] #[link_section = "__interrupt_vector_10"] pub static TIM0_VECTOR: unsafe extern "msp430-interrupt" fn() = tim0; unsafe extern "msp430-interrupt" fn tim0() { P1OUT.write(0x00); } ``` which generates the following assembly: ``` asm Disassembly of section __interrupt_vector_10: 0000fff2 <TIM0_VECTOR>: fff2: 10 c0 interrupt service routine at 0xc010 Disassembly of section .text: 0000c010 <_ZN3msp4tim017h3193b957fd6a4fd4E>: c010: c2 43 21 00 mov.b #0, &0x0021 ;r3 As==00 c014: 00 13 reti ... ```
2017-01-12resolve: Do not use "resolve"/"resolution" in error messagesVadim Petrochenkov-2/+2
2016-12-30Further and hopefully final Windows fixesSimonas Kazlauskas-1/+1
2016-12-26fix ui testJorge Aparicio-1/+1
2016-12-26More systematic error reporting in path resolutionVadim Petrochenkov-6/+4
2016-12-03Update error expectationsKeith Yeung-2/+2
2016-11-08Point to type argument span when used as traitEsteban Küber-1/+1
Given the following code: ```rust struct Foo<T: Clone>(T); use std::ops::Add; impl<T: Clone, Add> Add for Foo<T> { type Output = usize; fn add(self, rhs: Self) -> Self::Output { unimplemented!(); } } ``` present the following output: ```nocode error[E0404]: `Add` is not a trait --> file3.rs:5:21 | 5 | impl<T: Clone, Add> Add for Okok<T> { | --- ^^^ expected trait, found type parameter | | | type parameter defined here ```
2016-09-26Update E0425, E0446, E0449Jonathan Turner-1/+1
2016-09-15Fix wording for out-of-crate macro errorJonathan Turner-5/+5
2016-08-30Guard against platforms on which the sysv64 calling convention is not valid ↵CensoredUsername-1/+1
in non-codegen tests. Remove false positive in a test that relied on the exact formatting of an error string and rewrite the sysv64 register allocation test at it was triggering undefined behaviour
2016-08-17Replace local backtrace with def-use, repair std macro spansJonathan Turner-0/+88
2016-08-16RUST_NEW_ERROR_FORMAT is no moreSeo Sanghyeon-30/+16
2016-08-05Update E0404 to new format.Ryan Scott-1/+1
2016-08-01Fix fallout in `ui/codemap_tests`.Jeffrey Seyfried-5/+2
2016-07-14Add unicode test to ui testsJonathan Turner-0/+22
2016-07-14Add fix for tabs. Move error unit tests->ui testsJonathan Turner-0/+391
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 15:48:19 +0000