You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand it, trunks one and only entrypoint is fn main, which cannot be async, which means we cannot call async code in trunk apps, which is sad.
This came up today when I realized eframe::start_web is now async (since emilk/egui#2107), and eframe_template uses trunk. (This async stuff was added in order to support WebGPU).
The text was updated successfully, but these errors were encountered:
Hmm, this appears to be a misunderstanding. Trunk has nothing to do with the application which is ultimately executed/run in the browser. Trunk compiles and bundles assets, but does not dictate how the application itself is structured.
Any limitations on that front will be dictated by wasm-bindgen actually, which is the framework used to run rust wasm applications.
Please feel free to re-open if you think I have misunderstood your comments here :)
As I understand it,
trunk
s one and only entrypoint isfn main
, which cannot beasync
, which means we cannot callasync
code intrunk
apps, which is sad.This came up today when I realized
eframe::start_web
is nowasync
(since emilk/egui#2107), and eframe_template usestrunk
. (Thisasync
stuff was added in order to supportWebGPU
).The text was updated successfully, but these errors were encountered: