Pas__

u/Pas__


r/budapest•

If you are looking for tips on what to do, where to go, what to see, where to eat, please start with this amazing guide:

Vernazza's guide to Budapest

Currently Sziget festival is underway, and you should read that thread to find good advice that might be important to you if you are going to be in Budapest even if you don't plan on visiting the festival.

Just as a reminder, please keep in mind that Hungary (and Reddit) has zero tolerance for selling/buying/soliciting drugs. It might seem lik

727

r/budapest•

Up to date information for locals, travelers stuck here, and anyone just waking up from a coma, or simply curious about what's going on in this lovely empty city. If you think there's anything to add, mention it in the comments, and I'll edit the post.

​

Important: From 2020-03-28 00:00 for two weeks a curfew is in effect. (From 9-12 only senior citizens are allowed to go to shops/pharmacies. Going to work, caring for family members is okay, but the general point of the curfew is to keep physical contact to an even more minimal state. Try to wear a mask/scarf and glasses, but disinfect them at home - see methods below!)

Going for a walk/run/cycling is okay (even as a house

4472

r/rust•

Hello!

I wanted to understand a slide of OMG ITERATORS, and promptly failed.

use std::mem;
let mut data = vec![1,2,3,4];
let mut ptr1 = &mut data[0];
*ptr1 = 5;
println!("{}", ptr1);
{
    let mut fake_death = &mut ptr1;
}
mem::forget(ptr1);

// println!("{}", ptr1);
let mut ptr2 = &mut data[1];

And this naturally (?) gives the error: cannot borrow data as mutable more than once at a time error. Of course, if I uncomment the println! line, the compiler informs me that ptr1 is already long gone, yet somehow data is still borrowed. Oh, and the extra scope does nothing :/

Could someon

139

r/linux•

Newer CPUs have sort-of reliable devices for accurate timekeeping (see), but, as far as I know, CLOCK_MONOTONIC is available on systems without these nice guarantees.

So, what's the solution? It has simply worse resolution and then the kernel just uses the RTC? Or is there some clever mechanism that allows it to figure out how much time was spent in which power state and how much slower the clock was ticking in those intervals? (I doubt that, after all clock gating and frequency domains are very transparent to the software on top.) Or maybe the kernel just kee

06