intellij-rust/intellij-rust 3656
Rust plugin for the IntelliJ Platform
A simple, id-based arena
Automatic cfg for Rust compiler features
A simple chat implemented on top of async-std
CAD97/sorbus 22
An experimental reimplementation of rowan, focused on size efficiency
Repository to store student's practical works on high performance computing course
λ-llama code for ICFP contest 2016
pull request commentrust-analyzer/rust-analyzer
internal: overhaul expression attribute parsing
r+
comment created time in 7 hours
push eventmatklad/rust-analyzer
commit sha 56964c9bd383b80cf57df8d232876ada0686509f
feat: allow attributes on all expressions Attrs are syntactically valid on any expression, even if they are not allowed semantically everywhere yet.
push time in 7 hours
push eventmatklad/rust-analyzer
commit sha 7dc331faefe3f84daffa13ce7c0847fcf23fb279
fix: correct extend_to logic in parser Previously we swapped to events in the buffer, but that might be wrong if there aer `forward_parent` links pointing to the swapped-out node. Let's do the same via parent links instead, keeping the nodes in place
commit sha c2238b3e79e67ff180a128a9f80de2cb33469a42
feat: allow attributes on all expressions Attrs are syntactically valid on any expression, even if they are not allowed semantically everywhere yet.
push time in 7 hours
push eventrust-analyzer/metrics
commit sha 245fbbd9a326ac591a09da76d32f9fe1b4f39c50
📈
push time in 10 hours
push eventrust-analyzer/metrics
commit sha 26edef0878936bd6afc87b65f174d747cc2e2c39
📈
push time in 10 hours
push eventmatklad/drop_bomb
push time in 12 hours
push eventmatklad/drop_bomb
commit sha 90badbe910171d280b5d1e55422b7a099cf4c761
track caller
push time in 12 hours
push eventrust-analyzer/metrics
commit sha de2409b6c96b781178e0bff91a0bfad074cbf4df
📈
push time in 13 hours
push eventrust-analyzer/metrics
commit sha ad7d2033fde33e3bc77d9fadc4e8cceee3581f07
📈
push time in 14 hours
push eventrust-analyzer/metrics
commit sha 3bf746b438d9e24a4afd2cced129547b7eb1be80
📈
push time in 14 hours
push eventrust-analyzer/metrics
commit sha 23701e306d18ff39d57ae4b9692fbe12f138dd90
📈
push time in 14 hours
push eventrust-analyzer/metrics
commit sha 8082b888d163dee03032db7fc2728d5caa2bed17
📈
push time in 14 hours
push eventmatklad/rust-analyzer
commit sha f27cda6865fa33670a2e364388ecc56285feae30
minor: more condensed tests
commit sha 929fca5adcf0661f3427b30b3fb1053e04c82bea
minore: improve consistency
push time in 14 hours
push eventmatklad/rust-analyzer
commit sha d653995be4c7fd9095908ab614b5c24d767cc464
Merge #10343 10343: internal: parser cleanups r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
commit sha f692be853b485c036814fa22282943bc0437247c
minor: link my own pratt parsing article :-)
push time in 15 hours
push eventmatklad/config
commit sha 2f2c1cdbdc120ea300ecfa4ef8c3b97bcd395e44
.
push time in 15 hours
Pull request review commentnear/nearcore
feat: upgrade to wasmer2 via a protocol feature
impl NightshadeRuntime { .unwrap() .install(|| { contract_codes.par_iter().for_each(|code| {+ // FIXME: fetch the correct protocol version somehow?+ let current_protocol_version = ProtocolVersion::MAX;
Note to self: this is wrong in the absolute terms, but maybe fine in practice? Need to think more about this and write propper comment. here.
comment created time in 16 hours
push eventrust-analyzer/metrics
commit sha a3448f0871ec2ecb9f1f108694d81d8547808019
📈
push time in a day
issue closedrust-lang/rust
Decide whether `asm!` and/or `global_asm!` should be exported from the prelude.
In https://github.com/rust-lang/rust/issues/84019 it was decided that asm! and global_asm! should be defined in core::arch rather than be defined in the crate root. Whereas anything defined in the crate root is essentially "in the prelude" by necessity, being defined elsewhere means that we have the option of deciding whether or not these macros should be exported from the prelude.
In the original Zulip thread regarding which module these macros should be defined in, there was a small amount of discussion as to whether or not these should additionally be exported from the prelude: https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/namespacing.20.60asm!.60/near/233407632 . There did not seem to be a clear prevailing opinion.
Furthermore, I faintly recall from the most recent libs-api meeting someone mentioning that adding new macros to the prelude (or even the crate root) might be a compatibility hazard, and should only be done during an edition. I'm not sure if this is an official policy or not.
Note that this is not a blocker for asm! stabilization, as the item can be stabilized at arch::asm and exported from the prelude any time in the future.
closed time in a day
bstrie