about summary refs log tree commit diff
path: root/src/test/compile-fail
AgeCommit message (Collapse)AuthorLines
2011-10-12make compiler emit more than 1 error in the case of unsafeNiko Matsakis-3/+2
2011-10-12prohibit ptr deref unless in unsafe codeNiko Matsakis-0/+11
2011-10-12fix error msgNiko Matsakis-1/+0
2011-10-12add some new testsNiko Matsakis-1/+23
2011-10-12add pass to check that unsafe fns cannot be used as valuesNiko Matsakis-0/+9
2011-10-12all tests passNiko Matsakis-1/+1
2011-10-12skip test, remove whitespaceNiko Matsakis-0/+1
2011-10-12Add unsafe blocks, unsafe functions, and two rudimentary testsNiko Matsakis-0/+8
related to them
2011-10-11Don't allow bind to produce bare functionsBrian Anderson-0/+9
Issue #1022
2011-10-07Fix up test for last commitMarijn Haverbeke-1/+1
2011-10-07Add tests for programs that are invalid by arg-passing-styleMarijn Haverbeke-0/+9
Closes #1008
2011-10-07Add pass-by-ref annotation to the tests to make them typecheckMarijn Haverbeke-2/+4
Issue #1008
2011-09-28Test cases for #985Brian Anderson-0/+42
Other restrictions on pinned kinds happened to fix this Closes #985
2011-09-28Don't allow vectors of pinned kindsBrian Anderson-0/+11
Vectors of pinned kinds can't be safe because most interesting uses of vector perform copies
2011-09-28Make error patterns in some kind tests more specificBrian Anderson-5/+5
2011-09-28Revert "Revert "Implement pattern ranges for all numeric types.""Brian Anderson-0/+57
This reverts commit a034f87146e60e1db2327c6f6807c47406a1bb0b. Conflicts: src/comp/middle/check_alt.rs src/comp/middle/trans_alt.rs src/comp/syntax/ast.rs src/comp/syntax/ast_util.rs src/comp/syntax/fold.rs src/comp/syntax/print/pprust.rs Conflicts: src/comp/middle/trans_alt.rs
2011-09-27Patch to error instead of crashing when parsing unmatched double quotesWade Mealing-0/+8
Patch to error and fail instead of using all available memory then crashing to detect the error condition of an unmatched double quote before the end of a file. I couldn't get it to show nice error messages, so this may not be the ideal fix. A test case for this situation has also been added.
2011-09-27Make it again possible to initialize resource locals via assignmentBrian Anderson-20/+0
Some special cases allow both 'let a <- my_resource(x)' and 'let a = my_resource(x)' to work as expected despite ostensibly being copies and moves.
2011-09-27Prevent copies of resources into various thingsBrian Anderson-8/+20
2011-09-27Add xfailed tests that resources can't be copied into various thingsBrian Anderson-0/+68
2011-09-27Don't ever raise unique kinds of pinned kinds to shared (again)Brian Anderson-8/+39
So *resource, ~resource, [resource] are all pinned. This is counter to the design of the kind system, but this way is a much clearer path to type safety. Once we've established a good baseline with lots of tests, then we can try to make raising pinned kinds work.
2011-09-27Add an xfailed test for bogus deep copying of things containing resourcesBrian Anderson-0/+16
2011-09-27Add an xfailed test for bogus vector addition of typaramsBrian Anderson-0/+21
2011-09-26Add two xfailed tests for invalid copies into vectorsBrian Anderson-0/+36
2011-09-26Enforce copy restrictions on let initializersBrian Anderson-0/+29
2011-09-26Make some nocopy tests a bit more futureproofBrian Anderson-4/+4
Turn the let assignment initializers into move initializers since that assignment is going to become illegal
2011-09-26Prevent copying of uncopyable things via the copy opBrian Anderson-0/+10
2011-09-26Prevent copying of uncopyable things via compound assignment opsBrian Anderson-0/+9
2011-09-26Don't allow vectors of pinned kinds to be copiedBrian Anderson-0/+10
2011-09-26Don't allow copying of unique boxes of pinned kindsBrian Anderson-1/+0
Issue #409
2011-09-26Unique vectors and boxes of pinned are unique kinds. Closes #977Brian Anderson-36/+1
2011-09-24Don't iloop (future-proof test against improved reachability computations)Jesse Ruderman-1/+1
2011-09-24Remove irrelevant parts of testJesse Ruderman-4/+0
2011-09-24Move a previous run-pass test for kind-lowered unique boxes to compile-failBrian Anderson-0/+36
This test tries to swap unique boxes containing resources, which is not allowed. Issue #409
2011-09-24Unique pointers containing pinned kinds become pinnedBrian Anderson-0/+10
Issue #409
2011-09-22Calculate the correct kind for unique boxesBrian Anderson-0/+9
Issue #409
2011-09-22Don't unify unique boxes with different mutabilityBrian Anderson-0/+4
Issue #409
2011-09-21Revert "Implement pattern ranges for all numeric types."Marijn Haverbeke-57/+0
This reverts commit ce0f054f9d56df4e60291fc2e1b89ce979cf374f.
2011-09-21Implement pattern ranges for all numeric types.Josh Matthews-0/+57
2011-09-19Revert "xfail some tests that hang (instead of segfaulting) since eafb6789a2"Brian Anderson-5/+0
This reverts commit 5f44a1356e2b0adce5157f5e331ab9a55e891b0a. Issue #936
2011-09-19Revert "Revert "xfail some tests that hang (instead of segfaulting) since ↵Brian Anderson-0/+5
eafb6789a2"" This reverts commit 6eabe6f3f4b80e8c96286e266db64dfd0e576963.
2011-09-19Revert "xfail some tests that hang (instead of segfaulting) since eafb6789a2"Brian Anderson-5/+0
This reverts commit 5f44a1356e2b0adce5157f5e331ab9a55e891b0a. Issue #936
2011-09-18xfail some tests that hang (instead of segfaulting) since eafb6789a2Marijn Haverbeke-0/+5
See issue #936
2011-09-16Remove autoderef for callsMarijn Haverbeke-2/+0
We were only using it in a single place, and there for no discernable reason (probably as part of the bare-fn-vals-are-not-copyable plan). It seems more surprising than useful.
2011-09-16Change convention for specifying referenced argumentMarijn Haverbeke-1/+1
It is now 1-based, rather than 0 based. (Seems more natural, and allows 0 to be used to refer to self and maybe to closure.) Also allows non-referenced args to be implicitly copied again. Issue #918
2011-09-15Add tests for returning by referenceMarijn Haverbeke-0/+69
Issue #918
2011-09-13Print something when we can't figure out a tag name. Mitigates #876.Michael Sullivan-1/+1
2011-09-13Ensure that the declared type and actual type of a constant agreeMarijn Haverbeke-0/+4
Closes #899
2011-09-13Be more strict about what constitutes a block expressionMarijn Haverbeke-3/+2
Blocks (or statements involving blocks) that end in a semicolon are no longer considered the block-expression of their outer block. This used to be an expression block, but now is a statement block: { if foo { ret 1; } else { ret 10; } } This helps clear up some ambiguities in our grammar.
2011-09-13Make for loop alias-safeMarijn Haverbeke-2/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 18:54:03 +0000