Tootfinder

Update: it is not macros that cause this, it is plugins. If you use a build plugin, it injects the entire build plugin code into your resulting app.
Still no fix, but at least we know more.
Thanks to @… for narrowing down the problem.

Let's write a #macro in #Rust - Part 1
https://hackeryarn.com/post/rust-macros-1/

Today I learned about the true power of macros...and holy crap, they are awesome. Started back on the Z80 emulator and wondered if there was a way to reference procs in Nim using strings. Did some searching and came across someone who did something very similar and it never crossed my mind to even try this.
#nim

#TIL
> The macros describing this structure live in <asm/ioctl.h> and are
> _IO(type,nr) and {_IOR,_IOW,_IOWR}(type,nr,size). They use
> sizeof(size) so that size is a misnomer here: this third argument
> is a data type.
>
> Note that the size bits are very unreliable: in lots of cases they
> are wrong, either because of buggy macros using
> sizeof(sizeof(struct)), or because of legacy values.
#Linux

If you use Swift Macros in a library, use this script to remove 50 megs of junk that Xcode forces into your binaries:
https://github.com/migueldeicaza/GodotApplePlugins/blob/main/relink_without_swiftsyntax.sh
This has been a public …

Hey @…, I receive mails from a weird domain newgen.co, which looks super fishy to me. Is that really you?

In #FreeCAD, what can I do from the UI and from Python macros to cause all the topological naming links to be recreated in the current shape?
I have a Part Design Body that for which I can mark it to recalculate and then recalculate and it's fine, but if I modify a driving parameter trivially, including by an inconsequential .001mm, suddenly it tells me that I have an invalid edge …