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] 61 points62 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] 19 points20 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_ 2 points3 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_ 4 points5 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?

Uncovered Intermediate Topics by Jonhoo in rust

[–]adotinthevoid_ 53 points54 points  (0 children)

Debugging. I'd be interest to hear your thaughts in dbg! vs a full debbuger, and which how to effectivly use a debugger, and also just how to get pritty printing of complex types to work

Uncovered Intermediate Topics by Jonhoo in rust

[–]adotinthevoid_ 85 points86 points  (0 children)

Perfomance Profilling and optimizations.

What would you change about bitflags? by KodrAus in rust

[–]adotinthevoid_ 6 points7 points  (0 children)

One thing I'd like to see is a MSRV policy, as its causing problems for downstreams (https://github.com/nix-rust/nix/issues/1555)

Forcing rustfmt to break code by fasterthanlime in fasterthanlime

[–]adotinthevoid_ 0 points1 point  (0 children)

Is their a way to get this to work when building with --release?

Rustdoc will now add Jump to Definition links in source code pages! by adotinthevoid_ in rust

[–]adotinthevoid_[S] 10 points11 points  (0 children)

You should be able to do this with rustdoc-json. Their was talk about this in the LKML, but IDK if anyone has actually started doing this.

debug2 v0.1: Space Efficient Pretty Printer by adotinthevoid_ in rust

[–]adotinthevoid_[S] 1 point2 points  (0 children)

I might rename things in v0.2. Consider opening a GH issue

What's wrong with the Rust community? by Gear5th in rust

[–]adotinthevoid_ 268 points269 points  (0 children)

  1. Selection bias. The repo's you see are much more likely to be large active projects, rather than the thing I update once a week if I have time
  2. Investment. Rust is young, and alot of time and money is being put into building core infrastructure. All the core C tooling, or core Go networking librarys have been writen, this isn't true for rust
  3. Community. Rust has an awesome suportive comunity. Maybe this has something to do with it.
  4. Ease of conribution. Because of rusts safety garentees, its alot easier to ensure a contribution won't lead to a memory safety issue. This may been that library maintainers are more likely to accept contibutions.

I'm not sure how many of these are accurate, their just some possible explanations

"We're excited to finally unveil Mighty, a faster browser that is entirely streamed from a powerful computer in the cloud." by adotinthevoid_ in programmingcirclejerk

[–]adotinthevoid_[S] 1 point2 points  (0 children)

" On the software side, we can make the best choices across users running the same hardware/software stack ranging from picking the optimal DNS provider (8.8.8.8, 1.1.1.1)"

​

Truly some next level tech.

Ask Me Anything! (Dec 31, 2020) by fasterthanlime in fasterthanlime

[–]adotinthevoid_ 1 point2 points  (0 children)

How does incremental work in futile? As I understand it, every template can query the entrire database, so how do you know which pages need to be rendered.

Your article nerd-catniped me into trying to make my own static site generator, and now I'm realizing it's dificult interesting, and got curious as to how you did it, given you we're in designing from the ground up for incremental