Use trait objects (&dyn Fn()) when you need runtime polymorphism and don't mind the small performance cost of dynamic dispatch.
Use generics (F: Fn()) for better performance through static dispatch, but at the cost of potential code bloat due to monomorphization.
| # It's not documented, but you can use `package.metadata.component.bindings` to | |
| # set additional derive attributes for the generated bindings: | |
| [package.metadata.component.bindings] | |
| derives = ["serde::Serialize", "serde::Deserialize", "Hash"] |
Beetswap uses libp2p-core v0.42.0
Which means that any time you want to use Beetswap, you'll need core v0.42.0.
Oh, you want to use WebRTC though? That's fine.
Well, you'll need libp2p-webrtc-websys version 0.4.0 because anything before that breaks because __Nonexhaustive
was switched to __Invalid in wasm-bindgen.
So there's the web browser which everyone has, but JavaScript is slow and insecure.
But there's a bunch of tech out there that doesn't really need JavaScript; Rust => WebAssembly. So why are we bending over backwards to fit things into the browser?
What if we had a modular way to share "sites" that were really wasm apps. We could use 1 "wasm browser" and just run these apps.
If these wasm apps output a display to egui, we could load these wasm apps as plugins and just run the thing. Can we load a WIT component into egui and have it output the right display? If so, it's so on.
| // ensures you get compiler warnings if your type suddenly (unexpectantly) break autotraits | |
| // from Rust for Rustaceans Book | |
| mod tests { | |
| use ipns_entry::entry::IpnsEntry; | |
| fn is_normal<T: Sized + Send + Sync + Unpin>() {} | |
| #[test] |
| name: Build Rust & Deploy Leptos Page | |
| on: | |
| push: | |
| branches: ["master"] | |
| pull_request: | |
| branches: ["master"] | |
| # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages | |
| permissions: |
| local M = {} | |
| M.plugins = "custom.plugins" | |
| -- key mapping file | |
| M.mappings = require "custom.mappings" | |
| -- set our custom plugins.lua file here | |
| M.ui = { | |
| theme = "chadracula", |
With non-hardened keys, one can derive child public keys of a given non-hardened parent key without knowing any private key.
You cannot do this with hardened keys.
Knowledge of a parent extended public key plus any non-hardened private key descending from it is equivalent to knowing the parent extended private key (and thus every private and public key descending from it).
So let's say I want to find someone in Web3 by some contact information I have about them.
...whatever.
Let's assume there's a network where anyone can save this sort of information, like IPFS / libp2p.
| // relevant issue: | |
| https://github.com/sveltejs/kit/issues/2040 | |
| npm i typescript-transform-extensions ts-patch -D | |
| // tsconfig.json | |
| "plugins": [ | |
| { | |
| "transform": "typescript-transform-extensions", | |
| "extensions": { |
