profile
viewpoint
Who? Me?! mark-i-m operating systems, compilers, distributed systems, and chocolate. A follower of Jesus Christ :)

mark-i-m/jobserver 3

A jobserver for running experiments on test machines and copying results back.

mark-i-m/journey 2

Microbenchmarks for linux memory management system

mark-i-m/bus 1

Hacky CLI Utility to help me with buses...

mark-i-m/isb350c 1

A toy implementation of the ISB in verilog for our toy processor.

mark-i-m/backlight 0

Simple program to update the backlight brightness on my laptop

mark-i-m/BaseConverter 0

Converts any base (2 to 35) integer to any other base (2 to 35)

mark-i-m/beta.rust-lang.org 0

the home of the new rust website - now in beta!

mark-i-m/blog.rust-lang.org 0

The Rust Programming Language Blog

mark-i-m/bmk_linux 0

My collection of useful stuff for writing benchmarks on Linux ~4.4 (not very idiomatic or complete)

mark-i-m/bootloader 0

An experimental pure-Rust x86 bootloader

push eventmark-i-m/calculatrs

mark

commit sha f2978596cac88847e4c52cb32711348e155b2199

bump minor version

view details

push time in 13 hours

push eventmark-i-m/calculatrs

mark

commit sha 6b109465db91ef1686fc2e358f2814bc71606b62

fix out of bounds

view details

mark

commit sha bf8facda7201373a004f8c8448b5bd9f16537703

add alternate mult ops

view details

mark

commit sha a28cadd9531852ec17350198b8cdcc761c7be4d7

bump minor version

view details

push time in 13 hours

startedburaksezer/olric

started time in 15 hours

push eventmark-i-m/graph500

push time in 15 hours

create barnchmark-i-m/graph500

branch : 3.0.0-instrumented

created branch time in 15 hours

push eventmark-i-m/zeroing-perf

mark

commit sha f5b6ab6ab623c8848f3bc396eb34795fe0fd092b

add flags to makefile

view details

push time in 4 days

create barnchmark-i-m/zeroing-perf

branch : master

created branch time in 4 days

created repositorymark-i-m/zeroing-perf

Playing around with different ways to zero memory on x86

created time in 4 days

startedsaagarjha/TSOEnabler

started time in 5 days

pull request commentrust-lang/rustc-dev-guide

[WIP] Fix and clean up the terminology for stages

Ah, I didn't read carefully.

jyn514

comment created time in 6 days

pull request commentrust-lang/rustc-dev-guide

[WIP] Fix and clean up the terminology for stages

Ok, we discussed this extensively in today's meeting, and I think I'm now more on board with renaming the stages...

We also created this graphic: diagram.pdf

jyn514

comment created time in 6 days

startedmitosis-project/mitosis-asplos20-artifact

started time in 6 days

startedOpenRCT2/OpenRCT2

started time in 7 days

push eventmark-i-m/graph500

mark

commit sha 92274f79f1ea887009184cadba6753521115a867

replace int64 to uint64 everywhere

view details

mark

commit sha 0e41f716e01dfae960f9b8519e4d5bd94d339546

fix CSR vertex size

view details

mark

commit sha fd50a6f70636e767528bb29fd53eff70a46cd08f

fix validation

view details

push time in 7 days

push eventmark-i-m/graph500

mark

commit sha fd50a6f70636e767528bb29fd53eff70a46cd08f

fix validation

view details

push time in 7 days

pull request commentrust-lang/rust

mv std libs to library/

I don't know what to make of this other than maybe we messed up the layout of something in the processor caches? Where would one even start to debug something like this?

mark-i-m

comment created time in 7 days

push eventmark-i-m/graph500

mark

commit sha 0e41f716e01dfae960f9b8519e4d5bd94d339546

fix CSR vertex size

view details

push time in 7 days

create barnchmark-i-m/graph500

branch : dev

created branch time in 8 days

startedrepnop/mac_address

started time in 8 days

startedrepnop/vanadinite

started time in 8 days

push eventmark-i-m/graph500

mark

commit sha 68c6f0ccca9dae78650c5e5ed59ec2d2c07718b0

Change vertex labels to be u64

view details

push time in 8 days

push eventrust-lang/rustc-dev-guide

Takayuki Nakata

commit sha 4db8160fa3e7401c46443c1665db9404b091bbbf

Avoid "whitelist" Fixed according to https://github.com/rust-lang/rust/commit/62cf767a4a39b47677d18110359d9e7152dc9d1c

view details

Takayuki Nakata

commit sha 2cc652be17b8525f4c6c89c517381075e16a164e

Fix: crates -> a list of crates

view details

Takayuki Nakata

commit sha 04bd4ccd97d43cb7ee884fdf2d55f6cfeac64c81

Fix typo

view details

Takayuki Nakata

commit sha 44f1ab3bcf421b740bd8e2c8d9f214e2d05939a1

Some small fixes

view details

push time in 8 days

PR merged rust-lang/rustc-dev-guide

Avoid "whitelist" according to rust-lang/rust changes

Fixed according to https://github.com/rust-lang/rust/commit/62cf767a4a39b47677d18110359d9e7152dc9d1c.

+6 -7

0 comment

2 changed files

giraffate

pr closed time in 8 days

PR opened graph500/graph500

Fix a ton of lints

and set -Wall -Werror

This makes the compiler output much less noisy and thus makes the project code to work on.

+50 -49

0 comment

7 changed files

pr created time in 8 days

create barnchmark-i-m/graph500

branch : fix-lints

created branch time in 8 days

push eventmark-i-m/graph500

mark

commit sha 0e4e4d3afdad460d7f41691ab9a68c5139a531a2

fix a ton of lints

view details

push time in 8 days

Pull request review commentrust-lang/rustc-dev-guide

Avoid "whitelist" according to rust-lang/rust changes

 reasons:  TODO: what is the vetting process? -## Whitelist+## Pemitted dependencies -The `tidy` tool has a [whitelist] of crates that are allowed. To add a-dependency that is not already in the compiler, you will need to add it to this-whitelist.+The `tidy` tool has [crates that are allowed]. To add a

perhaps "a list of crates..."?

giraffate

comment created time in 8 days

push eventrust-lang/rustc-dev-guide

Takayuki Nakata

commit sha f75a2fb9b1c3ad50b030376c8159f33324aad3cc

Fix examples not working

view details

push time in 8 days

push eventrust-lang/rustc-dev-guide

Yuki Okushi

commit sha e54d59ca743296d75fb59750fb24d36300f252bb

Fix link/wording for `parse_nt`

view details

Yuki Okushi

commit sha 4e41d060c1f64e419c6702be861c20a5b5de437f

Prefer `::` than `.`

view details

push time in 8 days

PR merged rust-lang/rustc-dev-guide

Fix link/wording for `parse_nt`

Follow-up of https://github.com/rust-lang/rust/pull/74826

+6 -5

0 comment

1 changed file

JohnTitor

pr closed time in 8 days

Pull request review commentrust-lang/rustc-dev-guide

Fix link/wording for `parse_nt`

 we'll talk about that later.   analysis. The crate entry points for the parser are the `Parser.parse_crate_mod()` and   `Parser.parse_mod()` methods found in `librustc_parse::parser::item`. The external   module parsing entry point is `librustc_expand::module::parse_external_mod`. And-  the macro parser entry point is `rustc_expand::mbe::macro_parser::parse_nt`.+  the macro parser entry point is [`Parser.parse_nonterminal()`][parse_nonterminal].

Oh, I didn't notice that. Yeah, would you mind changing the other ones to :: too?

JohnTitor

comment created time in 8 days

Pull request review commentrust-lang/rustc-dev-guide

Fix link/wording for `parse_nt`

 we'll talk about that later.   analysis. The crate entry points for the parser are the `Parser.parse_crate_mod()` and   `Parser.parse_mod()` methods found in `librustc_parse::parser::item`. The external   module parsing entry point is `librustc_expand::module::parse_external_mod`. And-  the macro parser entry point is `rustc_expand::mbe::macro_parser::parse_nt`.+  the macro parser entry point is [`Parser.parse_nonterminal()`][parse_nonterminal].
  the macro parser entry point is [`Parser::parse_nonterminal()`][parse_nonterminal].
JohnTitor

comment created time in 8 days

push eventrust-lang/rustc-dev-guide

mark

commit sha 80c2dfd9d69eb4eea50143b40f51cbbfe86f258f

rewrite/update compiler source code chapter

view details

mark

commit sha 146635d7ff6c1be7bf2ee2dceb41bb45f734b76d

line length

view details

mark

commit sha 041e86cb9597e2031d9c7aaa4cf4036198c44048

fix typo

view details

mark

commit sha abd77148a404faecfe61ab4007a5c40785ea37df

add a bit more discussion of big picture

view details

mark

commit sha 0dab310a1bd95059d3afa1b7331c280857bd47ea

missing link

view details

Who? Me?!

commit sha fc7b7a5723e8e3eccf3b2c1800352156d365a645

Link to overview ch instead of internals Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

mark

commit sha 6f983169300c3e022b0dfb93f18099bd722bb75b

mention the overview chapter

view details

Who? Me?!

commit sha 5756aa3ecff83d691395b5250b8edb50547fe1f8

Typo Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

mark

commit sha f8dfca5001c2a8acccc0737950fd8a146a0f101c

some updates after std libs move

view details

Who? Me?!

commit sha cec6addcafa725640108dd8544524349e55fcdab

Typo Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

push time in 8 days

delete branch mark-i-m/rustc-guide

delete branch : update-source-ch

delete time in 8 days

PR merged rust-lang/rustc-dev-guide

Rewrite/update compiler source code chapter

cc @crlf0710

close #817

+207 -135

4 comments

1 changed file

mark-i-m

pr closed time in 8 days

issue closedrust-lang/rustc-dev-guide

Changes after std move to library

The first section of this chapter need to be reword: https://github.com/rust-lang/rustc-dev-guide/blob/master/src/compiler-src.md

The main Rust repository consists of a src directory, under which there live many crates. These crates contain the sources for the standard library and the compiler. This document, of course, focuses on the latter.

Could be rewritten as: The main Rust repository consists of two directory: src and library, under which there live many crates. library contains the sources for the standard library. While src is where compiler and its components live. This document, of course, focuses on the latter.

closed time in 8 days

lzutao

push eventmark-i-m/rustc-guide

Who? Me?!

commit sha 514560876e84491570fb6ed0865c75445478a0e7

Typo Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

push time in 8 days

issue commentgraph500/graph500

segmentation fault on single-node run for scale24-25

I'm running into this as well. I would like to use graph500 on a single huge-memory node (1TB DRAM), but I keep getting a segfault at anything larger than a toy problem. Is there a possibility of have an ifdef to define the type of the indices?

yvdriess

comment created time in 8 days

pull request commentrust-lang/rustc-dev-guide

[WIP] Give overview of MIR dataflow framework

Friendly ping @ecstatic-morse :) I know you're busy -- just wanted to make sure this is still on your radar.

ecstatic-morse

comment created time in 8 days

pull request commentrust-lang/rustc-dev-guide

Update HIR chapter to reflect the removal of `NodeId`s

Friendly ping @LeSeulArtichaut

LeSeulArtichaut

comment created time in 8 days

Pull request review commentrust-lang/rustc-dev-guide

Suggest system llvm or assertions

 cp config.toml.example config.toml ```  Then you will want to open up the file and change the following-settings (and possibly others, such as `llvm.ccache`):+settings (and possibly others, such as `llvm.ccache`). Also, see the notes+below about LLVM-related settings.  ```toml-[llvm]-# Indicates whether the LLVM assertions are enabled or not-assertions = true

Sorry, looking over this PR again after a while. We add the suggestion to turn this on below. Are you suggesting that we suggest always turning it on (and if they use system LLVM it doesn't matter)?

mark-i-m

comment created time in 8 days

Pull request review commentrust-lang/rustc-dev-guide

Suggest system llvm or assertions

 incremental = true verbose-tests = true ``` +Moreover, there are a couple of other configs to consider, depending on whether+you are planning to work on something LLVM-related.++If you are planning to work on LLVM-related things, you may want to enable+assertions for improved debugging. This comes at a cost in compile time:++```toml+[llvm]+# Indicates whether the LLVM assertions are enabled or not.+assertions = true+```++If you are _not_ planning to work on LLVM-related things, you can avoid+building LLVM altogether by using a system LLVM:

I think the UI tests should always pass, right? Most of them are long before LLVM runs. I would expect it to only matter for codegen. Is there a particular example you are thinking of?

mark-i-m

comment created time in 8 days

push eventmark-i-m/rustc-guide

Who? Me?!

commit sha 64bbe7aabb3c569d0a648910eee739ec751bfc93

toml highlighting Co-authored-by: Yuki Okushi <huyuumi.dev@gmail.com>

view details

push time in 8 days

pull request commentrust-lang/rustc-dev-guide

Name `rustbuild` instead of saying 'the bootstrap binary'

Is there a particular PR on rust-lang/rust that this is blocked on?

jyn514

comment created time in 8 days

pull request commentrust-lang/rustc-dev-guide

Rewrite/update compiler source code chapter

@jyn514 Friendly ping :) It would be nice to merge this soon.

mark-i-m

comment created time in 8 days

push eventmark-i-m/rustc-guide

Who? Me?!

commit sha 093b9032de1821f8a9f507f80f985aca1920858b

Upgrade to mdbook 0.4 and switch to book parts (#764) * upgrade to mdbook 0.4 and switch to book parts * update linkcheck * fix links, update about-this-guide

view details

Who? Me?!

commit sha e7db51facac88729e5dc9ec63ea233c1bc6a9be0

Fix formatting

view details

Who? Me?!

commit sha b183202f37201529fb8da326b541eabc6e4acbd1

Fold chapters by default to make ToC shorter

view details

Aaron Hill

commit sha b7095995aa2b55b23922d412ac40a784b640a8a4

Add 'recovery' to the gloassary

view details

Joshua Nelson

commit sha c1c66a82f2e6d177c2d47ea69315d22b929a6b62

Revamp bootstrapping section - Move most of the overview to building/bootstrapping.md - Add things besides stages to bootstrapping.md

view details

Joshua Nelson

commit sha 1c68f636cf2d80ec7a64f6ffeb205ebca3764285

Improve wording and fix typos Co-authored-by: Who? Me?! <mark-i-m@users.noreply.github.com>

view details

Joshua Nelson

commit sha be8c8bb7bc52f1b1b231a91da350770235ee0d48

Fix line lengths

view details

pierwill

commit sha 2c6f17671f727b30cd274832b550f2e0428784d2

Edit ty.md Makes various edits throughout for formatting, punctuation, and typo fixes. Also makes some edits and re-wording for clarity.

view details

Yuki Okushi

commit sha 19f7d2e77d16de9a31b1be2bfe6ef7b910b75739

Rename resolvers following the latest rustc change (#776)

view details

Who? Me?!

commit sha fd4c83f4ab5d1432646e09a75c6e5d11f117d87d

Move Errors and Lints to Analysis

view details

Who? Me?!

commit sha 99745b99312c04fc1e64520048f8dc3f54d1b451

Move Getting Started to a "prefix chapter"

view details

mark

commit sha fe7856889a138eced7caa9b0faf43860fdebdc87

fix file name

view details

pierwill

commit sha 0006f199151dbda14c936ab078f971bdd8754983

Edit Part 2 introduction (#777) * Edit Part 2 introduction * needs a pause Co-authored-by: Tshepang Lekhonkhobe <tshepang@gmail.com>

view details

mark

commit sha b1198eff6ba9b6cb29f53c37ceccccd742084ab5

move CONTRIBUTING.md to rustc-dev-guide

view details

mark

commit sha 431df827e2e6adea1ee44f23219ac91d926eed90

line length

view details

mark

commit sha dbaa12ec12330fbf52b0f66c643ba38528b186f5

fix links

view details

mark

commit sha e82626f802d2822a20ea2cd21d3a17f61cebaf23

fix links

view details

Who? Me?!

commit sha c2c219af6cb0758d0b07df95d1a9336146b31a2f

Fix non-link Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

Who? Me?!

commit sha 00b67a55de5ec17d5477ffca5906d5a068286b91

Escape other non-link Co-authored-by: Joshua Nelson <joshua@yottadb.com>

view details

mark

commit sha b85f30d01357163b253622ffa671743029b7d651

fix links

view details

push time in 8 days

pull request commentrust-lang/rust

Move DelaySpanBugEmitted to ty::context

Ping @eddyb. I think this should be a relatively easy PR to review.

mark-i-m

comment created time in 8 days

push eventmark-i-m/rust

Joshua Nelson

commit sha a5275ff41521bb8e5a70f49f8ed420eaac7ed7de

Don't run everybody_loops for rustdoc Instead, ignore resolution errors that occur in item bodies. The reason this can't ignore item bodies altogether is because `const fn` could be used in generic types, for example `[T; f()]`

view details

Joshua Nelson

commit sha b3187aabd20637e0bb9a930b4b930a079b785ca9

Don't run analysis pass in rustdoc - Explicitly check for missing docs - Don't run any lints except those we explicitly specified

view details

Joshua Nelson

commit sha 1b8accb7497e6fe66be331e40f8663d198a6b648

Add an option not to report resolution errors for rustdoc - Remove unnecessary `should_loop` variable - Report errors for trait implementations These should give resolution errors because they are visible outside the current scope. Without these errors, rustdoc will give ICEs: ``` thread 'rustc' panicked at 'attempted .def_id() on invalid res: Err', /home/joshua/src/rust/src/libstd/macros.rs:16:9 15: rustc_hir::def::Res<Id>::def_id at /home/joshua/src/rust/src/librustc_hir/def.rs:382 16: rustdoc::clean::utils::register_res at src/librustdoc/clean/utils.rs:627 17: rustdoc::clean::utils::resolve_type at src/librustdoc/clean/utils.rs:587 ``` - Add much more extensive tests + fn -> impl -> fn + fn -> impl -> fn -> macro + errors in function parameters + errors in trait bounds + errors in the type implementing the trait + unknown bounds for the type + unknown types in function bodies + errors generated by macros - Use explicit state instead of trying to reconstruct it from random info - Use an enum instead of a boolean - Add example of ignored error

view details

Dylan MacKenzie

commit sha 14a8707cde48c7914af307f4687056d829ad2de9

Add `rustdoc` tests from #72088

view details

Joshua Nelson

commit sha 768d6a4950d66f1a0e1e7793a984fb638494d1c5

Don't ICE on errors in function returning impl trait Instead, report the error. This emits the errors on-demand, without special-casing `impl Trait`, so it should catch all ICEs of this kind, including ones that haven't been found yet. Since the error is emitted during type-checking there is less info about the error; see comments in the code for details. - Add test case for -> impl Trait - Add test for impl trait with alias - Move EmitIgnoredResolutionErrors to rustdoc This makes `fn typeck_item_bodies` public, which is not desired behavior. That change should be removed once https://github.com/rust-lang/rust/pull/74070 is merged. - Don't visit nested closures twice

view details

Joshua Nelson

commit sha a93bcc9a7b8e48865d3df59fc936a0553e4d1e37

Recurse into function bodies, but don't typeck closures Previously, rustdoc would issue a delay_span_bug ICE on the following code: ```rust pub fn a() -> impl Fn() -> u32 { || content::doesnt::matter() } ``` This wasn't picked up earlier because having `type Alias = impl Trait;` in the same module caused _all closures_ to be typechecked, even if they wouldn't normally. Additionally, if _any_ error was emitted, no delay_span_bug would be emitted. So as part of this commit all of the tests were separated out into different files.

view details

Joshua Nelson

commit sha d01044305a5f2eb177521f51a7d7bfaee1ccf688

Add test case for #65863

view details

Joshua Nelson

commit sha cf844d2eabc8929edb0923d71ec6ff076ac3428b

Don't make typeck_tables_of public

view details

Joshua Nelson

commit sha 0cbc1cddcc6b9657fb727e35dce753d38e52cc52

Avoid unnecessary enum Just use a boolean instead.

view details

Joshua Nelson

commit sha 3576f5d7e153d10aae36b2be067bc6243a4c77db

Address review comments about code style

view details

Joshua Nelson

commit sha bbe4971095717912463d8dbc00ba8ce9a5988963

Don't crash on Vec<DoesNotExist>

view details

Joshua Nelson

commit sha 2f29e696ab0ced54f016bed0514a53f6e281ac8a

Mention `cargo check` in help message

view details

Joshua Nelson

commit sha 763d373dabb7ccf581737749a2a1adec335d8249

Use tcx as the only context for visitor Previously two different parts of the context had to be passed separately; there were two sources of truth.

view details

Joshua Nelson

commit sha 0759a55feff2d7c4a15b563adc087ac4f59acb1b

Remove unnecessary lifetime parameter TyCtxt is a reference type and so can be passed by value.

view details

Joshua Nelson

commit sha 2d0e8e2162a2e2be233a63ba5a8cbf3e19770b17

--bless

view details

Joshua Nelson

commit sha 02a24c8e2fd370041a24b7d93e8c3710b7b76015

Don't ICE on infinitely recursive types `evaluate_obligation` can only be run on types that are already valid. So rustdoc still has to run typeck even though it doesn't care about the result.

view details

Joshua Nelson

commit sha 4c88070c87b81c3cf6c8409a78c35ebdf67a67c3

Use mem::replace instead of rewriting it

view details

Joshua Nelson

commit sha b2ff0e703eef715737ebb2afab04ec3f73cbf4bf

Fix comment

view details

Joshua Nelson

commit sha ac9157b482e916c09e2ec35bb7e514ae7b6b9c03

EMPTY_MAP -> EMPTY_SET

view details

Joshua Nelson

commit sha 6eec9fb5d15d2bb2025398f5cae12aebe03d87e8

Address review comments - Move static variables into the innermost scope in which they are used - Clean up comments - Remove external_providers; rename local_providers -> providers

view details

push time in 8 days

delete branch mark-i-m/graph500

delete branch : newreference

delete time in 8 days

delete branch mark-i-m/graph500

delete branch : v2-spec

delete time in 8 days

delete branch mark-i-m/graph500

delete branch : v3-wip

delete time in 8 days

startedIBM/fhe-toolkit-linux

started time in 9 days

push eventrust-lang/rustc-dev-guide

Yuki Okushi

commit sha d89c8c9b12ede0df2cf2ed3e8fa04b6edece8310

Rename `HAIR` to `THIR`

view details

Yuki Okushi

commit sha 61824dde4f47e5a2a8f2c56c63daece1eed2c578

Mention `HAIR` to clarify

view details

push time in 9 days

PR merged rust-lang/rustc-dev-guide

Rename `HAIR` to `THIR`

rust-lang/rust#74582 is merged, let's cut our hair here as well :) The nightly rustc doc isn't updated so the links are currently broken. Closes #806

+20 -19

0 comment

4 changed files

JohnTitor

pr closed time in 9 days

issue closedrust-lang/rustc-dev-guide

Rename `HAIR` (High-level Abstruct IR) to `THIR` (Typed HIR) in this guide

Follow-up of https://github.com/rust-lang/rust/pull/74582 This proposes to rename HAIR to THIR and it'll be likely accepted. We have some mention of HAIR here, so the follow-up work will be needed as Niko said. I'll work on this but in case let's create an issue just as a reminder.

closed time in 9 days

JohnTitor

push eventrust-lang/rustc-dev-guide

Yuki Okushi

commit sha c7a3bca8291ba5e8e3e161d9428c4f3c5dced5db

Adjust mentions about CI to GitHub Actions

view details

Yuki Okushi

commit sha 5d8a8c832b84d3985f6abdc41f9eedbcb0a1f00a

Address review comment

view details

push time in 9 days

PR merged rust-lang/rustc-dev-guide

Adjust mentions about CI to GitHub Actions

So, we've migrated our CI to GitHub Actions almost, except for macOS. There're some mentions to Pipelines and even Travis in the guide, let's replace them with GHA. I don't think we have to mention macOS build but any suggestions are welcome.

+24 -18

0 comment

5 changed files

JohnTitor

pr closed time in 9 days

Pull request review commentrust-lang/rustc-dev-guide

Rename `HAIR` to `THIR`

-# HAIR and MIR construction+# THIR and MIR construction 

Could you add a note that THIR used to be called HAIR? That way people that come across comments or old discussions have some context.

JohnTitor

comment created time in 9 days

pull request commentrust-lang/rust

Substantial refactor to the design of LineWriter

@Lucretiel Yeah, all of the paths in that command are now in library/ and don't have the "lib" prefix:

python3 x.py test --target wasm32-unknown-emscripten \
    --exclude library/core \
    --exclude library/alloc \
    --exclude library/proc_macro \
    --exclude library/std \
    --exclude library/term \
    --exclude library/test

If you find yourself running unexpected tests, it might be a bug in my PR...

Lucretiel

comment created time in 10 days

issue commentrust-lang/rustc-dev-guide

Changes after std move to library

Sorry, I've been a bit swamped lately. This is on my list. There is still some change going on, especially wrt to src/librustc_*. #815 fixed a bunch of stuff.

lzutao

comment created time in 11 days

startedubnt-intrepid/polyfuse

started time in 11 days

startedvmware/hillview

started time in 13 days

delete branch mark-i-m/rust

delete branch : patch-1

delete time in 13 days

delete branch mark-i-m/highfive

delete branch : patch-1

delete time in 13 days

startedgithub/roadmap

started time in 13 days

pull request commentrust-lang/rust

Implement the `min_const_generics` feature gate

@rustbot modify labels: +A-const-generics

lcnr

comment created time in 13 days

pull request commentrust-lang/highfive

Update highfive rotation paths

also cc @nikomatsakis so you know why you're getting so many new PRs!

mark-i-m

comment created time in 13 days

pull request commentrust-lang/rust

Re-enable linkcheck after moving std

Rebased. Should be ready for r+

mark-i-m

comment created time in 14 days

push eventmark-i-m/rust

Ximin Luo

commit sha 1f25a4b3ae87327f045fbfec82b5af4c8da6ecd6

config.toml.example: Update remap-debuginfo doc to be more general & accurate

view details

Ximin Luo

commit sha 84896c7f096c38d43e020612e639e5975aee7f34

rustbuild: use Display for exit status instead of Debug, see #74832 for justification

view details

Ximin Luo

commit sha 3dcab2922c4eaaea11a6856fa566bdb7a6d9c1f6

rustbuild: format both Ok/Err separately, since Result doesn't do it

view details

Ximin Luo

commit sha e7089a97e79fb550dcd76da47c614b2701963327

rustbuild: refactor how the wrapper deals with exit codes

view details

Joshua Nelson

commit sha 617d10975ef1db8ab9fcf3b5720a147f36b69f41

Separate `missing_doc_code_examples` from intra-doc links These two lints have no relation other than both being nightly-only. This allows stabilizing intra-doc links without stabilizing missing_doc_code_examples.

view details

Joshua Nelson

commit sha def61777083d938a75718d55ba6c6600d4923d6d

Move `look_for_tests` to `private_items_doc_tests`

view details

Joshua Nelson

commit sha d34a1b0c1b4b22cc61b5956c07d89517bf278af8

Don't duplicate builder code - Add Builder::new_internal

view details

Joshua Nelson

commit sha 0192fa4786db80d2c9888af98e7ceec47d327887

Make the default stage dependent on the subcommand ### x.py build/test: stage 1 I've seen very few people who actually use full stage 2 builds on purpose. These compile rustc and libstd twice and don't give you much more information than a stage 1 build (except in rare cases like https://github.com/rust-lang/rust/pull/68692#discussion_r376392145). For new contributors, this makes the build process even more daunting than it already is. As long as CI is changed to use `--stage 2` I see no downside here. ### x.py bench/dist/install: stage 2 These commands have to do with a finished, optimized version of rustc. It seems very rare to want to use these with a stage 1 build. ### x.py doc: stage 0 Normally when you document things you're just fixing a typo. In this case there is no need to build the whole rust compiler, since the documentation will usually be the same when generated with the beta compiler or with stage 1. Note that for this release cycle only there will be a significant different between stage0 and stage1 docs: https://github.com/rust-lang/rust/pull/73101. However most of the time this will not be the case.

view details

Joshua Nelson

commit sha f7dcfcd45bd019acf8c914c204ccae519c420adc

Don't build rustc without std - Set rustc to build only when explicitly asked for This allows building the stage2 rustc artifacts, which nothing depends on. Previously the behavior was as follows (where stageN <-> stage(N-1) artifacts, except for stage0 libstd): - `x.py build --stage 0`: - stage0 libstd - stage1 rustc (but without putting rustc in stage0/) This leaves you without any rustc at all except for the beta compiler (https://github.com/rust-lang/rust/issues/73519). This is never what you want. - `x.py build --stage 1`: - stage0 libstd - stage1 rustc - stage1 libstd - stage1 rustdoc - stage2 rustc This leaves you with a broken stage2 rustc which doesn't even have libcore and is effectively useless. Additionally, it compiles rustc twice, which is not normally what you want. - `x.py build --stage 2`: - stage0 libstd - stage1 rustc - stage1 libstd - stage2 rustc - stage2 rustdoc and tools This builds all tools in release mode. This is the correct usage for CI, but takes far to long for development. Now the behavior is as follows: - `x.py build --stage 0`: - stage0 libstd This is suitable for contributors only working on the standard library, as it means rustc never has to be compiled. - `x.py build --stage 1`: - stage0 libstd - stage1 rustc - stage1 libstd - stage1 rustdoc This is suitable for contributors working on the compiler. It ensures that you have a working rustc and libstd without having to pass `src/libstd` in addition. - `x.py build --stage 2`: - stage0 libstd - stage1 rustc - stage1 libstd - stage2 rustc - stage2 libstd - stage2 rustdoc This is suitable for debugging errors which only appear with the stage2 compiler. - `x.py build --stage 2 src/libstd src/rustc` - stage0 libstd - stage1 rustc - stage1 libstd - stage2 rustc - stage2 libstd - stage2 rustdoc, tools, etc. - stage2 rustc artifacts ('stage3') This is suitable for CI, which wants all tools in release mode. However, most of the use cases for this should use `x.py dist` instead, which builds all the tools without each having to be named individually.

view details

Joshua Nelson

commit sha 01c6256178fb126d668045f3a1297e0f3491e985

Change debuginfo to default to 1 if `debug = true` is set From [a conversation in discord](https://discordapp.com/channels/442252698964721669/443151243398086667/719200989269327882): > Linking seems to consume all available RAM, leading to the OS to swap memory to disk and slowing down everything in the process Compiling itself doesn't seem to take up as much RAM, and I'm only looking to check whether a minimal testcase can be compiled by rustc, where the runtime performance isn't much of an issue > do you have debug = true or debuginfo-level = 2 in config.toml? > if so I think that results in over 2GB of debuginfo nowadays and is likely the culprit > which might mean we're giving out bad advice :( Anecdotally, this sped up my stage 1 build from 15 to 10 minutes. This still adds line numbers, it only removes variable and type information. - Improve wording for debuginfo description Co-authored-by: Teymour Aldridge <42674621+teymour-aldridge@users.noreply.github.com>

view details

Joshua Nelson

commit sha 74b373426a79af2b21b8d266a881753e338cfd2e

Fix most bootstrap tests Uses --stage 2 for all the existing tests

view details

Joshua Nelson

commit sha 60c17297383102964ae08bed7e0d2f202959f7f9

Move tests into a submodule

view details

Joshua Nelson

commit sha cdca33754771e6b10e9399c8d7780e391963305e

Add tests for the new behavior - Only set stage 2 in dist tests - Add test for `x.py doc` without args - Add test for `x.py build` without args - Add test for `x.py build --stage 0`

view details

Joshua Nelson

commit sha 4ee8d847e5f411e178fa5224d16dae38affb9392

Use --stage 2 explicitly in CI - expand yaml anchors - don't use --stage 2 for dist; that's already the default

view details

Joshua Nelson

commit sha 7768eaa0503e7e98eb2404fa4664297a84d72d38

Add assert that tests happen with stage 2 in CI - Use stage 2 for makefile - Move assert to builder - Don't add an assert for --help - Allow --stage 0 if passed explicitly - Don't assert defaults during tests Otherwise it's impossible to test the defaults!

view details

Joshua Nelson

commit sha a5337d668c4976fed89551f94b03b2903f8f947c

Use exhaustive match for assert

view details

Joshua Nelson

commit sha c3f5556c30e7af7a9fe139a2393b0fcdd27b9206

private_items_doc_tests -> doc_test_lints

view details

bors

commit sha 1454bbd4fdac9b7272b93fe82860613dccc0afad

Auto merge of #74841 - infinity0:fix-exec, r=Mark-Simulacrum rustbuild: use Display for exit status instead of Debug, see #74832 for justification

view details

bors

commit sha 1f5d69daccd1f04e42886d9aaf513f2691132d17

Auto merge of #74855 - jyn514:separate-lints, r=Manishearth Separate `missing_doc_code_examples` from intra-doc links These two lints have no relation other than both being nightly-only. This allows stabilizing intra-doc links without stabilizing `missing_doc_code_examples`. Fixes one of the issues spotted by @ollie27 in https://github.com/rust-lang/rust/pull/74430#issuecomment-664693080. r? @Manishearth

view details

bors

commit sha 2c28244cf0fc9868f55070e55b8f332d196eaf3f

Auto merge of #74796 - infinity0:master, r=nikomatsakis config.toml.example: Update remap-debuginfo doc to be more general & accurate This makes it more obvious that the work-around to #74786 is actually correct, and a custom `--remap-path-prefix` isn't needed. In fact the previous comment `/rustc/$hash/$crate` was wrong, it is not `$crate` but whatever path exists in the rustc source tree, so either `src/$crate` or `vendor/$crate`. I've fixed that as well to avoid future confusion.

view details

push time in 14 days

pull request commentrust-lang/rust

mv std libs to library/

I mean, I don't Niko has that much on his plate 😛

mark-i-m

comment created time in 14 days

pull request commentrust-lang/highfive

Update highfive rotation paths

cc @petrochenkov who alerted me to this in the first place

mark-i-m

comment created time in 14 days

PR opened rust-lang/highfive

Update highfive rotation paths

r? @Mark-Simulacrum

+9 -9

0 comment

1 changed file

pr created time in 14 days

push eventmark-i-m/highfive

Who? Me?!

commit sha f404fc7554174011ad4ee13ba5aa0607780bd5b5

Update highfive rotation paths

view details

push time in 14 days

fork mark-i-m/highfive

Github hooks to provide an encouraging atmosphere for new contributors

fork in 14 days

issue commentrust-lang/compiler-team

Move the compiler to a new `compiler/` directory

  • There is still some ongoing discussion on zulip about what to do with rustc_llvm, rustllvm and llvm-project.
  • There is also a possibility of renaming the directories to drop the rustc_ prefix (but keep the crate names and transition those slowly over time).
  • I updated the proposal to be rustc/src/main.rs, as you proposed.
mark-i-m

comment created time in 14 days

push eventmark-i-m/rust

mark

commit sha ad7a81c5db08eebae17823b93e4b66a905d35ed2

binary is now compiler/rustc/src/main.rs

view details

push time in 14 days

pull request commentrust-lang/rust

std: Switch from libbacktrace to gimli (take 2)

Just a heads up that backtrace should be added to library/ now instead of src/.

alexcrichton

comment created time in 14 days

startedbanach-space/clang-tutor

started time in 14 days

pull request commentrust-lang/rustc-dev-guide

Add basic steps for a new target

Yeah, this is a weird failure. I restarted CI...

shepmaster

comment created time in 14 days

push eventmark-i-m/rust

mark

commit sha fe502e52a7a978af9a55fb2631e5cbcbee3657d4

fix some tools

view details

push time in 14 days

pull request commentrust-lang/rust

[WIP] Move almost all compiler crates to compiler/

Do you plan to introduce the inner src directories though?

Yes, you beat me to it :) I just pushed a commit.

I had some reservations regarding llvm (including #74787) and tests,

Yeah, I think those will be the big questions here... It might be reasonable to do those in a followup PR.

mark-i-m

comment created time in 14 days

push eventmark-i-m/rust

mark

commit sha e2866e5581fcc04071307a6f21a2b2bf4c3a299e

nested src

view details

push time in 14 days

Pull request review commentrust-lang/rust

[WIP] Move almost all compiler crates to compiler/

 [workspace] members = [   "src/bootstrap",-  "src/rustc",-  "src/librustc_codegen_llvm",+  "compiler/bin",+  "compiler/rustc_codegen_llvm",

Indeed, you are right.

mark-i-m

comment created time in 14 days

push eventmark-i-m/rust

mark

commit sha 755367dfafb4f1958842c1f64c2f6150d20adcb2

remove rustc_codegen_llvm from root cargo.toml

view details

push time in 14 days

push eventmark-i-m/rust

mark

commit sha 1a3b12d42f9bd0c9c1f81db8007932004f29b5ef

compiler/bin -> compiler/rustc

view details

push time in 14 days

pull request commentrust-lang/rust

[WIP] Move almost all compiler crates to compiler/

r? @ghost for now

mark-i-m

comment created time in 14 days

PR opened rust-lang/rust

[WIP] Move almost all compiler crates to compiler/

This mostly me playing around at this point... there is an MCP here that has not been accepted yet: https://github.com/rust-lang/compiler-team/issues/336

+900 -902

0 comment

1648 changed files

pr created time in 14 days

create barnchmark-i-m/rust

branch : mv-compiler

created branch time in 14 days

PR opened rust-lang/rust

Reenable tests after moving std

r? @Mark-Simulacrum

+10 -13

0 comment

2 changed files

pr created time in 14 days

create barnchmark-i-m/rust

branch : mv-std-followup

created branch time in 14 days

issue openedrust-lang/compiler-team

Move the compiler to a new `compiler/` directory

Proposal

(this is a successor of #316, primarily to restart the discussion with a smaller scope)

In MCP #298 and https://github.com/rust-lang/rust/pull/73265, we moved the standard libraries into their own library/ directory at the root of the repo. In this proposal, we follow through to reorganize the compiler source into a new compiler/ directory:

- library/        // as in #298 
- compiler/
  - librustc_* -> rustc_*
  - rustc/ -> bin/rustc.rs
  - llvm-project (submodule)
  - test/ (only compiler tests)
- src/      // unchanged

The primary goals of this proposal are to

  1. make it more obvious where things live by separating out distinct-ish parts of the project into different top-level directories
  2. help (especially new) contributors to feel less overwhelmed by the size of the project by breaking the top-level directories down into more manageable and modular parts
  3. work towards a world in which std/core and/or other parts of the project can be built independently of the compiler
  4. make the repo a bit more ergonomic for contributors

Note that in particular, we move some things around:

  • The src/test directory is split up to compiler/test and src/test/
  • We remove the lib* prefixes for all the crates

Unresolved question: there was a proposal on the zulip thread for #316 to move the llvm-project submodule out of the compiler src directory (e.g. to the root of the repo). This would make it easier to grep in the compiler/ directory. (Personally, I like this idea).

Unresolved question: there was also some questions about what to do with the current rustc crate (effectively, the main.rs of the compiler), which is basically just a main function that calls rustc_driver. In the above proposal, I have it as bin/rustc.rs.

Implementation: I propose we do this move over multiple PRs to reduce conflicts. I think it should be less painful than moving the std libs, and should largely be editing Cargo.toml, but it would be nice to avoid the problems of https://github.com/rust-lang/rust/pull/73265, where a bazillion things needed to be updated.

Approval: We anticipate bikeshedding over names, exact paths, and etc. The approval of this MCP will be construed as a green light to start working on PRs, but not as consensus on the exact final form. Rather, a separate FCP or nomination will be required to merge e.g. the PR that moves compiler/.

Followup: In followup MCPs similar to this one, we will move around other parts of src until we reach an acceptable state.

Mentors or Reviewers

@Mark-Simulacrum mentored/seconded #298, but I don't know if they wish to mentor/second this MCP. @Dylan-DPC also expressed interest in working on this.

Process

The main points of the Major Change Process is as follows:

  • [x] File an issue describing the proposal.
  • [ ] A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • [ ] Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

created time in 14 days

issue closedrust-lang/compiler-team

MCP: Reorganize the rust-lang/rust repo directory structure

Proposal

EDIT(mark-i-m): Updated as per feedback

In #298 (accepted), we decided to move the standard libraries into their own std/ directory at the root of the repo. In this proposal, we follow through to reorganize the compiler source into a new compiler/ directory:

- std/        // as in #298 
- compiler/
  - librustc_* -> rustc_*
  - rustc/ -> bin/rustc/
  - llvm-project (submodule)
  - test/ (only compiler tests)
- src/      // unchanged

The primary goals of this proposal are to

  1. make it more obvious where things live by separating out distinct-ish parts of the project into different top-level directories
  2. help (especially new) contributors to feel less overwhelmed by the size of the project by breaking the top-level directories down into more manageable and modular parts
  3. work towards a world in which std/core and/or other parts of the project can be built independently of the compiler

Note that in particular, we move some things around:

  • The src/test directory is split up to compiler/test and src/test/

Approval: We anticipate a lot of bikeshedding over names, exact paths, and etc. We propose to resolve disagreements so as to match whatever consensus is reached with respect to similar discussion on std/ (e.g. whether to have src/ directories). Moreover, the approval of this MCP will be construed as a green light to start working on PRs, but not as consensus on the exact final form. Rather, a separate FCP will be required to merge e.g. the PR that moves compiler/.

Followup: In followup MCPs similar to this one, we will move around other parts of src until we reach an acceptable state.

Mentors or Reviewers

If you have a reviewer or mentor in mind for this work, mention then here. You can put your own name here if you are planning to mentor the work.

I suspect that a lot of help will be needed from different parts of the different teams. @Mark-Simulacrum mentored/seconded #298, but I don't know if they wish to mentor/second this MCP. @dylan-dpc also expressed interest in working on this.

Process

The main points of the Major Change Process is as follows:

  • [x] File an issue describing the proposal.
  • [ ] A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • [ ] Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

closed time in 14 days

mark-i-m

pull request commentrust-lang/rust

mv std libs to library/

Yeah, I think the intent was to do it one shot to avoid corrupting the git history too much...

(also, lol, I think this conflicted with literally the entire PR queue)

mark-i-m

comment created time in 14 days

PR opened rust-lang/rust

Update outdated readme
+1 -1

0 comment

1 changed file

pr created time in 14 days

push eventmark-i-m/rust

Who? Me?!

commit sha 62fd2c81e36f0efadf4c5fc8e5576bcdfb66ac18

Update outdated readme

view details

push time in 14 days

delete branch mark-i-m/rust

delete branch : mv-std

delete time in 14 days

pull request commentrust-lang/rust

mv std libs to library/

🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉

mark-i-m

comment created time in 14 days

pull request commentrust-lang/rust

mv std libs to library/

@bors r=Mark-Simulacrum,mark-i-m

mark-i-m

comment created time in 14 days

push eventmark-i-m/rust

Adam Perry

commit sha d275739c09f266479d6db388cbf55ba6ca791b9d

Derive common traits for panic::Location. Add documentation about the host/target behavior of Location::file.

view details

Adam Perry

commit sha 416dc4b978e5921cd0b20478a17f048dd378bdff

Clarify core::panic::Location's docs on ordering. Co-authored-by: Simon Sapin <simon.sapin@exyr.org>

view details

Bastian Kauschke

commit sha 104cb878e34da2f66c0d0b7e5ed388a2c5b96b58

add `PredicateKint`, because who doesn't like bodging

view details

Bastian Kauschke

commit sha 9a33b5915467259b4487adbc451422134003f223

minimal

view details

Matthew Jasper

commit sha 1b33f39126c56192e7e35bc943bee9cca6960abd

Handle trait/projection predicates with bound regions correctly

view details

Bastian Kauschke

commit sha cd30894c2f7113bf79c7f66d30a774f11b315d3f

anonymize_predicate

view details

Bastian Kauschke

commit sha fb36c8bc80b4d8f071317adbb05337c9a0a2dbae

query_outlives_constraints_into_obligations

view details

Bastian Kauschke

commit sha c1d244ffd881f59f1c8e5b7bdce38a1a80a0f7d6

convert trivial predicates

view details

Bastian Kauschke

commit sha 653f56af53c01c38f34f0926dd13ee391a290fa0

wf

view details

Bastian Kauschke

commit sha 1fda8c207e083acabace5a66d16824a52b43061d

somewhat related cleanup

view details

Bastian Kauschke

commit sha 7f39b0c9ab7c2c3beeb9dd3a54f51b3a5f7e21a0

subst_supertrait

view details

Bastian Kauschke

commit sha 4c3b1e89cff55b1f337c5c95c4988ea5a82e2441

elaborate

view details

Bastian Kauschke

commit sha 506f4308b757e64ceb9e894e27265c103593cd9e

progress

view details

Bastian Kauschke

commit sha 9852b42b581bbc4843460f4654a2dbd859bd9034

`PredicateKint` -> `PredicateKind`, the beginning of the end

view details

Bastian Kauschke

commit sha b79f7fbda86748909a6a833521b2fab97de6e654

rustdoc

view details

Bastian Kauschke

commit sha 8d4c99ad88169689ce560ad05eedf60de1d5e9c4

clippy

view details

Bastian Kauschke

commit sha bbd581c583a7168359bf94beaa111d6ad3316837

fix elaborate for predicates with unbound variables

view details

Bastian Kauschke

commit sha c6c0d17c8d6be89c6ef00de14fbafaf76d276d55

review

view details

Bastian Kauschke

commit sha 1151d6204919202340e22cef15ca69aa183b41d1

split ignore_qualifiers

view details

Bastian Kauschke

commit sha 562d4784215cb477c7fcec7c2c34df898d59c674

fix rustdoc

view details

push time in 14 days

more