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
The current sledgehammer is archived, which is also why it's present at #1421 , but work is still ongoing in sledgehammer_bindgen - so it would be great to have that present instead.
The text was updated successfully, but these errors were encountered:
birkskyum
changed the title
sledgehammer-bindgen
sledgehammer -> sledgehammer-bindgen
Oct 17, 2023
@ealmloff Are you interested in contributing a new implementation?
I would be happy to, but before I implement anything sledgehammer-bindgen is a bit different from the original sledgehammer library. It makes the generates bindings for something like the original sledgehammer. I'm not sure what kind of implementation would be more useful here.
I could implement it similar to the existing sledgehammer and wasm-bindgen version with generalized dom manipulation bindings. Those bindings are similar to what Dioxus or Leptos could use internally.
Or I could implement bindings that are specific to the task that would be more similar to the Vanillajs implementation with WASM doing all of the heavy compute. This would be the kind of bindings that something like Kobold or a svelte implementation in rust could use. This would probably be faster and closer to the optimal wasm web framework baseline, but I don't want to include something that is against the spirit of the benchmark.
The current sledgehammer is archived, which is also why it's present at #1421 , but work is still ongoing in sledgehammer_bindgen - so it would be great to have that present instead.
The text was updated successfully, but these errors were encountered: