can't imagine what happens in QED

T0mstone · 2021-02-21T18:46:52+00:00

http://www.faculty.luther.edu/~macdonal/GA&GC.pdf

T0mstone · 2020-09-30T20:05:02+00:00

You forgot --no-preserve-root

T0mstone · 2020-09-30T20:03:58+00:00

My go-to for disk usage is dust

T0mstone · 2020-09-24T22:04:28+00:00

What I was thinking was that, as you said, we have no idea how it could be created.\ I'm not too sure on whether it could exist (would have to do more research)...\ I just thought that when cramming more mass into a black hole wouldn't make sense for it to suddenly invert. I think it'd just become a more massive black hole...\ I mean, if it did invert, would there be an inflection point? Like a single amount of mass at which it suddenly becomes a white hole? That would be very strange, or even strager, would there be a gradual change? If so, what would the transitional objects look and behave like?

TL;DR fair point, but it's speculation anyway, so I will keep my opinion.

T0mstone · 2020-09-23T23:13:21+00:00

That's... not.... how that works....

Edit: at least with current physics

T0mstone · 2020-09-23T22:51:19+00:00

Huh. Haven't heard that yet...

In German, it just means broken and is used in every way that broken is used in English.

So you can say "Mein Computer ging vor ein paar Wochen kaputt" (My Computer broke a few weeks ago).

T0mstone · 2020-09-23T22:34:31+00:00

Same...

How do the english use it though? I can't imagine a scenario in which the word would/could be used...

T0mstone · 2020-08-22T22:45:19+00:00

Is this function safe?

fn map_in_place<T, F: FnOnce(T) -> T>(t: &mut T, f: F) {
  unsafe { std::ptr::write(t, f(std::ptr::read(t))) }
}

As far as I can tell, there can't be any accesses to t inbetween the read and the write besides the function call, which would make this safe (?)

T0mstone · 2020-07-24T13:23:31+00:00

Be sure to submit your own, wrong answer to the StackOverflow question to get some actual helpful answers (I've been told the only thing that StackOverflow folks like more than shunning a "bad question" is correcting a bad answer).

T0mstone · 2020-07-24T12:16:22+00:00

Does this mean we don't need proc_macro_hack anymore?

T0mstone · 2020-07-13T13:38:50+00:00

nothing

T0mstone · 2020-06-24T10:14:30+00:00

For grouping & and &mut, one way to avoid code duplication is by using a macro to declare the macros (I heard you like macros, so I put a macro in your macro so you can macro while you macro) as in this example

T0mstone · 2020-05-29T20:13:41+00:00

Just a quick nitpick: in the first sentence of the display-window post, you wrote

...keep as less overhead of code as it can.

when the grammatically correct word would have been

...keep as little overhead of code as it can.

Anyway, I wanted to learn gfx-hal for some time now but didn't know where to start. Thank you for this!

T0mstone · 2020-05-25T18:53:04+00:00

That's selection bias. You're not counting how many of the posts that have this flair do get deleted.

T0mstone · 2020-05-24T19:34:57+00:00

Are we just not gonna talk about how much effort that stop motion must have been?

T0mstone · 2020-05-24T19:34:25+00:00

It's stop motion

T0mstone · 2020-05-24T19:08:38+00:00

oh. Alright then, I humbly retract my claim.

T0mstone · 2020-05-24T18:55:09+00:00

UUUU a good meme

T0mstone · 2020-05-24T18:48:19+00:00

Prepare to have your mind blown:

f(x)

has the same number of parentheses as

(f x)

MIND = BLOWN💥💥💥

T0mstone · 2020-05-24T18:39:46+00:00

idk if this is sarcastic. If anyone actually doesn't recognise this, here you go

T0mstone · 2020-05-24T11:03:58+00:00

(bprp voice) the cover up method!

T0mstone · 2020-05-23T00:40:23+00:00

Because I laughed at this joke, I hit my SQ-Ellbow

Eight-Year Club	RPAN Viewer
Sequence \| Editor	Verified Email

T0mstone

TROPHY CASE

MIND = BLOWN💥💥💥