Show newer

@b0rk

I really appreciate that, in all cases I remember, you are more specific than "don't start weird arguments", and would be happy if you continued that.

(The reason for my appreciation is that being more specific (a) helps me not fret on whether what I intend to do follows the request (b) intimates that specificity and directness are part of norms of the space, so let's me fret less about people being unhappy with what I'm doing without telling me that in an effective fashion.)

@amin

This might even be solidarity with yourself at some future point in time.

A funny place where that happens in imo many cities is buying paper public transit tickets (as opposed to using some kind of app).

@janboehm Was ist die Besonderheit des Pistaziencroissants? Ich kann mich nicht erinnern solches zu sehen, aber würde es nicht ausserordentlicher als ein nüssiges finden.

@gsuberland

Ah, wait, the macro seems to affect the names of the functions that are compiled into libgcc, and not the names used to call them.

@gsuberland

WDYM by address? If these functions were dynamically linked, the address would be found at dynamic linking time, so I assume they are statically linked and included in the piece of code you're generating.

You probably could mess with a custom linker script, so that the relocations that address those functions would be handled differently. You could also use DECLARE_LIBRARY_RENAMES (gcc.gnu.org/onlinedocs/gccint/) to point them at other named functions.

I'm not sure what you want to happen when these functions are called. I presume you'd want to write your own versions of them (that will e.g. proxy to ones already-present in the target). That you should be able to do with either of the approaches above.

Disclaimer: I might be unaware of some additional specialness of softfloat functions from the POV of gcc.

@rygorous

I always thought that the reason for the limit was not wires, but heating (mostly radiative) of various things around the bulb (e.g. the plastic around the socket). That obviously also depends only on the total emitted power, but ISTM less preposterous that something could have changed there.

@grrrr_shark have you considered asking at a Brocki? This might be out of their league, but they do deal with at least some large objects.

@dalias
Or, have the instance promulgate different contents of the toot to different people without making any indication that it was edited.

@mjg59 @penguin42

nordtronic seems to be making such: nordtronic.com/shop/box-relay-

I have never seen one irl, so can't say anything useful about them though.

@mcc

Such sinks exist at least in medical settings (as an alternative to an elbow-operated tap, so that you can wash your hands and not touch the handle afterwards).

@Janik @samueldr

Nit: done as in created or reviewed (I first thought you just meant created, and started wondering about reviews).

Algorithm suggestion 

@loke

If you need to accept a stream of rectangles as input (i.e. can't keep all of them in memory), then you can keep a priority queue for the "rectangle end" events, where you'd insert an event when you encounter a beginning of a rectangle.

Algorithm suggestion 

@loke

You can use a broom: have a data structure that represents what's going on in a single row that can be updated. Whenever you move to a new row, update it to take into account rectangles that appear or disappear in that row (which you can find by having a list of rectangle starts and ends and sorting that instead of just the list of rectangles).

The candidate for such a structure is a sorted dictionary that maps left ends of intervals to their IDs and right ends. You can simply amend it (by adding/removing the appropriate entry) and you can construct the spans by iterating over it while keeping aside a stack of still-open rectangles.

@james@strangeobject.space I really like that it is very explicit about the main issue being advertising.

@b0rk

An IMO common variant of (b) is "this thing existed for a totally different reason and was good enough here". I mention this explicitly, because it's a variant of (b) that can happen without ~any passage of time.

description of injury 

@whitequark

Note that "retained" doesn't mean that it goes back to normal. It's apparently (based on a few random websites) very common for the pulp to become necrotic (because it has lots its blood supply and that apparently has very little chance of reconnecting reasonably) and thus for the tooth to require root canal treatment.

@soupglasses @delroth @FedericoSchonborn

If those maintainers were employed earlier by someone else (and their job was not maintaining nix/nixpkgs) then how does that change the time/energy/work situation?

(I agree that it might create a conflict of interest situation, but don't see how it shifts available work away.)

@msw @whitequark @filippo @attie @brown

In a transactional relationship with upstream why would you ever send patches upstream?

@mcc

The backlight of the departures board of my train station is curiosly partially broken. (I'm somewhat surprised that the edges of the broken area are that sharp.)

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.