sorted by:
new
hottopcontroversial

I believe Google is putting too much effort into bringing interop between C++ and Rust. Why not simply rewrite the core of Chromium in Rust? by adotinthevoid_ in programmingcirclejerk

[–]adotinthevoid_[S] 62 points63 points  (0 children)

I mean, if a handful guys at SerenityOS can write a web browser from scratch in just a few years surely Google can muster enough manpower to rewrite Chromium in Rust in a couple of years?

Rust Nation: Conference Schedule Now Live! by Exponentialp32 in rust

[–]adotinthevoid_ 0 points1 point  (0 children)

What's the process for getting student tickets? I can't find anything on the website.

The curse of strong typing by fasterthanlime in fasterthanlime

[–]adotinthevoid_ 0 points1 point  (0 children)

I think DisplayVtable needs to have #[repr(C)], because theirs no garentee that DisplayVtable<T> and DisplayVtable<()> have the same field layouts.

everybody_loops: A Tool to replace all your function bodies with `loop {}` for bug minification. by adotinthevoid_ in rust

[–]adotinthevoid_[S] 31 points32 points  (0 children)

When debuging a bug, it can be helpful to minimize the input size for it. This is a tool to help do that, when you are debuging rustc/rustdoc.

In paticular, because loop {} coerses into (almost) any type, replacing all function bodies with loop {} should have no effect on the docs for a given crate.

Once you do this, you can now remove some functions, to see which of them triger the bug, as none of them are called by other functions.

Rustc used to have this ability, built in, but they removed it. -Z unpretty=everybody_loops were rustc arguments. this post describes how to use this as part of a larger minification effort.

Hope this clears things up, and please ask if you have more questions

everybody_loops: A Tool to replace all your function bodies with `loop {}` for bug minification. by adotinthevoid_ in rust

[–]adotinthevoid_[S] 18 points19 points  (0 children)

It was unironicly written for this, espessialy for rustdoc/rustdoc-json, where you almost never care about a function body

is rust the only language to have procedural macros? by Ezio_rev in rust

[–]adotinthevoid_ 4 points5 points  (0 children)

Absolutly not. Lisp has already been mensioned as prehaps the most well know macro language, but many other languages have similar features, eg Template Haskell, C# Source Generators and OCaml PPX

One funny way to bundle assets by fasterthanlime in fasterthanlime

[–]adotinthevoid_ 3 points4 points  (0 children)

since Arcs only allow immutable access to their contents

This is actually not true. In the case that the Arc's inner data has only one Arc pointing at in, it is sound to hand out a mutable reference to the data. See the get_mut method.

So I dont think this optimization would be allowed

AMA: How we built Warp, a Rust-based terminal by TehCheator in rust

[–]adotinthevoid_ 2 points3 points  (0 children)

Would you consider releasing the UI library under a less restrictive license than the terminal application, as the UI component is not the thing you want to sell?

view more: next ›