mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7,681 Commits 2 Branches 0 Tags 1.4 GiB
1c54744e3f
Commit Graph

7681 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Kevin Cantu
1c54744e3f fixing indentation 2012-01-23 22:28:25 -08:00
Kevin Cantu
ff95029171 Added str::words_iter 2012-01-23 22:28:25 -08:00
Kevin Cantu
d4b287e852 Added str::any, str::bytes_iter, str::windowed, and vec::windowed functions 2012-01-23 22:28:25 -08:00
Kevin Cantu
0493a7c87d Added str::map and str::all functions 2012-01-23 22:28:25 -08:00
Tim Chevalier
477c3a8eb1 Merge branch 'master' into tag-docs 2012-01-23 22:22:07 -08:00
Brian Anderson
ab0eed34fd rustdoc: Prune unexported items from the doc tree 2012-01-23 22:13:34 -08:00
Tim Chevalier
c7d5e79fd8 Register snapshots 2012-01-23 21:54:09 -08:00
Brian Anderson
6766d0ead0 cargo: Long lines 2012-01-23 21:14:48 -08:00
Brian Anderson
5e9ca11c8d cargo: Remove unused imports - work around mystery resolve failure 2012-01-23 21:08:13 -08:00
Brian Anderson
3d08840f34 Merge pull request #1628 from startling/cargo-descriptions 
Implemented package descriptions for cargo
 2012-01-23 20:46:33 -08:00
tim
2c3cd1749e Added a newline after each description. 
`<@graydon> maybe an extra newline to make the grouping clearer?`
 2012-01-23 21:50:32 -06:00
tim
65840f3625 Get description attribute for packages from json. 2012-01-23 21:42:29 -06:00
Niko Matsakis
5e13d19cc0 s/block()/fn()/g 2012-01-23 19:06:33 -08:00
tim
dfae48736f Steps towards package descriptions. 
I added a description field for `package` objects (it's read from
a literal string for now) and `print_pkg` now prints descriptions if
they're there.
 2012-01-23 20:23:31 -06:00
Brian Anderson
04351a84ca core: Format comm docs correctly 2012-01-23 18:07:05 -08:00
Brian Anderson
ef941998be rustdoc: Correctly indent multiline fn signatures 2012-01-23 17:58:52 -08:00
Brian Anderson
17ac98ba22 rustdoc: Use the standard markdown syntax for code blocks 2012-01-23 17:58:52 -08:00
Brian Anderson
7d5d1a311e test: Add no-reformat directive to compile-fail/issue-1362 2012-01-23 17:37:15 -08:00
Kevin Atkinson
664d9cc86f Add regression test for issue #1362. 
Although its not really needed.  Without that fix, reported spans will
likely be bogus if the error is within the first couple of lines
(probable around 5) of that file.  Thus, many of the compile-fail
tests will fail due to incorrect location.
 2012-01-23 17:37:15 -08:00
Kevin Atkinson
5e60facf78 Add regresion tests for issue #1448 and #1387. 2012-01-23 17:37:15 -08:00
Kevin Atkinson
4795e19d6d When replacing a pattern variable in macro expansion use the span of 
the replacement and not the span of the pattern variable.

Fixes issue #1448, and #1387.
 2012-01-23 17:37:15 -08:00
Kevin Atkinson
20ab47fe49 Allow ast_fold_precursor to change the span. 
This involved changing the prototype for the callbacks to thread the
span though.  A wrapper function, fold::wrap, can be used to wrap the
old style callbacks.
 2012-01-23 17:37:15 -08:00
Kevin Atkinson
ad21d9c64a Don't reset the chpos/byte_pos to 0 in new_parser_from_source_str. 
This correctly fixes issue #1362.

chpos/byte_pos are now the offsets within a particular file, but
rather the offsets within a virtual file with is formed by combing all
of the modules within a crate.  Thus, resetting them to 0 causes an
overlap and hence, bogus source locations.

Fix #1362 by moving chpos/byte_pos to parse_sess so that
new_parser_from_source_str has access to them and hence can chose an
initial value that is not already been used in the crate.

Note that the trigger for bug 1361 was that syntax/ext/expand.rs calls
parse_expr_from_source_str (which calls new_parser_from_source_str)
using the same codemap as the current crate (and hence causing overlap
with files in the crate as new_parser_from_source_str resets the
chpos/byte_pos to 0).
 2012-01-23 17:37:15 -08:00
Kevin Atkinson
355edf13e7 Change "file" of injected string from "-" to "<anon>", less confusing 
that way.
 2012-01-23 17:37:14 -08:00
Kevin Atkinson
1625a4320d Revert "rustc: Exclude stdin from codemap files when lookup_pos". 
Need a better fix, right now it is just causing even more confusion,
for example in issue #1448 and #1387.

This reverts commit 1e4de33374.
 2012-01-23 17:37:14 -08:00
Brian Anderson
93e9600a94 core: Write docs that format correctly in markdown or pandoc 2012-01-23 17:11:01 -08:00
Brian Anderson
3239f81898 core: More doc tweaks 2012-01-23 17:03:42 -08:00
Brian Anderson
7d58797453 core: Reformat the crate docs to look nicer 2012-01-23 16:58:30 -08:00
Brian Anderson
24b425567c wip 2012-01-23 16:49:29 -08:00
Brian Anderson
4e2d8d8051 core: Add crate docs 2012-01-23 16:40:51 -08:00
Tim Chevalier
cd9b344f7b Update docs to reflect new export forms 2012-01-23 16:35:39 -08:00
Brian Anderson
368daf8b5a Change rustc and rustdoc's #[desc] attribute to #[comment] 
There are two attributes in use for this same purpose.
 2012-01-23 16:25:20 -08:00
Brian Anderson
50d8e9f2a1 Revert "rustdoc: Get the crate brief description from the 'desc' attr" 
This reverts commit 521e58a3c4.

Some crates use 'desc', some 'comment' - I want them to just use 'doc'
 2012-01-23 16:23:08 -08:00
Brian Anderson
f4c31bda62 rustdoc: Print return value descriptions on same line as type 2012-01-23 16:18:01 -08:00
Brian Anderson
fa3368bc71 rustdoc: Prune undocumented return values 2012-01-23 16:18:01 -08:00
Brian Anderson
a7d3544d10 rustdoc: Don't prune functions with documented arguments 2012-01-23 16:18:01 -08:00
Brian Anderson
5cff7c093e rustdoc: Prune undocumented fn args 2012-01-23 16:18:01 -08:00
Niko Matsakis
5660b8bfb5 add msgsend.rs to benchmarks 2012-01-23 16:04:14 -08:00
Tim Chevalier
6db688e893 Check that the names mentioned in tag exports are actually types (or variants) 
Check that in export foo{}, foo is an enum type, and that in export
foo{bar, quux}, foo is an enum type and bar and quux are variants belonging
to foo.
 2012-01-23 15:48:08 -08:00
Tim Chevalier
9dc59e1506 Export all enum variants by default; new syntax for selectively exporting variants 
See issue 1426 for details. Now, the semantics of "export t;" where t is a tag are
to export all of t's variants as well. "export t{};" exports t but not its
variants, while "export t{a, b, c};" exports only variants a, b, c of t.

To do:
- documentation
- there's currently no checking that a, b, c are actually variants of t in the
 above example
- there's also no checking that t is an enum type, in the second two examples above
- change the modules listed in issue 1426 that should have the old export
semantics to use the t{} syntax

I deleted the test export-no-tag-variants since we're doing the opposite now,
and other tests cover the same behavior.
 2012-01-23 15:48:08 -08:00
Brian Anderson
e515999324 rustdoc: Prune undocumented modules 2012-01-23 15:40:01 -08:00
Brian Anderson
521e58a3c4 rustdoc: Get the crate brief description from the 'desc' attr 2012-01-23 15:16:14 -08:00
Brian Anderson
7857dcb88c rustdoc: Add a script for running rustdoc output through markdown/pandoc 2012-01-23 15:16:14 -08:00
Brian Anderson
7c1d1d6c9a doc: Just remove mention of the busted win installer from INSTALL.txt 2012-01-23 14:15:40 -08:00
Brian Anderson
afc3abc317 Merge pull request #1621 from thoughtpolice/install-dot-txt 
Add an INSTALL.txt
 2012-01-23 14:14:32 -08:00
Brian Anderson
088e915fee Remove mention of Windows installer from tutorial 
We don't want users to hurt themselves, since the installer has
a bug in 0.1 that could possibly corrupt %PATH%

Conflicts:

	doc/tutorial.md
 2012-01-23 14:09:21 -08:00
Austin Seipp
62c4d2ce82 Add an INSTALL.txt and make it part of the source distribution 2012-01-23 16:07:01 -06:00
Brian Anderson
0143e52580 Merge pull request #1620 from thoughtpolice/email-fix 
Fix my email in AUTHORS.txt
 2012-01-23 14:01:07 -08:00
Brian Anderson
6cf8ea779b Add Matthew O'Connor to AUTHORS.txt 2012-01-23 13:59:59 -08:00
Brian Anderson
123d5df723 Merge pull request #1618 from oconnor0/patch-1 
Point to correct cargo-central.
 2012-01-23 13:57:49 -08:00