Feat: massive changes to definition of components
This change switches back to the original `ctx<props>` syntax for commponents. This lets lifetime elision to remove the need to match exactly which lifetime (props or ctx) gets carried to the output. As such, `Props` is currently required to be static. It *is* possible to loosen this restriction, and will be done in the future, though only through adding metadata about the props through the Props derive macro. Implementing the IS_STATIC trait is unsafe, so the derive macro will do it through some heuristics. For now, this unlocks sharing vnodes from parents to children, enabling pass-thru components, fragments, portals, etc.
This commit is contained in:
1 parent
c1fd848f89
commit
508c560320
82 files changed
+692
-558
No files matched your search
@@ -17,7 +17,7 @@ fn main() {
|
||||
.expect("Webview finished");
|
||||
}
|
||||
|
||||
static Example: FC<()> = |ctx, _props| {
|
||||
static Example: FC<()> = |ctx| {
|
||||
ctx.render(html! {
|
||||
<div>
|
||||
<svg class="octicon octicon-star v-align-text-bottom"
|
||||
@@ -36,7 +36,7 @@ static Example: FC<()> = |ctx, _props| {
|
||||
</div>
|
||||
})
|
||||
};
|
||||
// static Example: FC<()> = |ctx, _props| {
|
||||
// static Example: FC<()> = |ctx| {
|
||||
// ctx.render(rsx! {
|
||||
// div {
|
||||
// class: "flex items-center justify-center flex-col"
|
||||
|
||||
Reference in new issue
Block a user