I've been using Unity Burst compilation for years to great effect, but only now learned that the supported function signatures are completely different depending on whether they're entry points (marked with [BurstCompile]) or non-entry points (no attribute, but called from another Burst function).
So just adding [BurstCompile] to everything that should be Burst-compilable doesn't work, as you lose the ability to return structs on all such functions.
Not easy to tell from the docs or errors.
Rune Skovbo Johansen
npub1qf…5dns6
2026-10-26 08:59:07 UTC
Author Public Key
npub1qf7tmqvjd6mpfu8vg8ffnpfs8vkdldyt5p7ljh4alfjeep5222ks25dns6Seen on
wss://relay.momostr.pinkPublished at
2026-10-26 08:59:07 UTCEvent JSON
{
"id": "b42f3cbae50c82ede163edd1f41f36d510b7744ee523c68339f99ad5d940e47b",
"pubkey": "027cbd81926eb614f0ec41d29985303b2cdfb48ba07df95ebdfa659c868a52ad",
"created_at": 1793005147,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.gamedev.place/@runevision/117506385369713634",
"web"
],
[
"proxy",
"https://mastodon.gamedev.place/users/runevision/statuses/117506385369713634",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.gamedev.place/users/runevision/statuses/117506385369713634",
"pink.momostr"
],
[
"-"
]
],
"content": "I've been using Unity Burst compilation for years to great effect, but only now learned that the supported function signatures are completely different depending on whether they're entry points (marked with [BurstCompile]) or non-entry points (no attribute, but called from another Burst function).\n\nSo just adding [BurstCompile] to everything that should be Burst-compilable doesn't work, as you lose the ability to return structs on all such functions.\n\nNot easy to tell from the docs or errors.",
"sig": "df30fb0f8747cb7ceb59a671e58e462ce1b5be920fd48d5dbb14442bd42a6b44fade6279d88192a3a0ddf257fe729be5b3cfb9ef1db71457a054f3867051cb52"
}