Fix autocompletion in html macro for rust-analyzer

[mohe2015]

Description

In rust-analyzer it was not possible to get autocompletion suggestions inside of expression in the html! macro. This change should fix that. The first part is removing usage of the vec! macro as that seemed to hinder autocompletion and the second part is allowing to parse invalid expressions so rust-analyzer gets some output from the macro.

Checklist

• I have reviewed my own code
• I have added tests. No, I think this is not testable

[github-actions]

Size Comparison

Details

examples	master (KB)	pull request (KB)	diff (KB)	diff (%)

✅ None of the examples has changed their size significantly.

[github-actions]

Visit the preview URL for this PR (updated for commit b4185b5):

https://yew-rs-api--pr3829-improve-html-macro-r-kd57veoz.web.app

_{(expires Sun, 30 Mar 2025 12:31:24 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[github-actions]

Benchmark - SSR

Yew Master

Details

Benchmark	Round	Min (ms)	Max (ms)	Mean (ms)	Standard Deviation
Baseline	10	310.534	312.089	310.958	0.573
Hello World	10	517.917	530.502	520.950	3.846
Function Router	10	1613.039	1647.988	1622.170	9.668
Concurrent Task	10	1005.853	1007.201	1006.554	0.397
Many Providers	10	1075.049	1104.422	1088.400	10.447

Pull Request

Details

Benchmark	Round	Min (ms)	Max (ms)	Mean (ms)	Standard Deviation
Baseline	10	291.024	293.614	291.339	0.800
Hello World	10	489.334	554.961	512.441	20.939
Function Router	10	1605.408	1675.083	1620.642	20.122
Concurrent Task	10	1004.884	1007.057	1006.329	0.709
Many Providers	10	1139.608	1210.778	1167.338	28.674

[Madoshakalaka]

@its-the-shrimp does this make sense?

[its-the-shrimp]

@its-the-shrimp does this make sense?

Sure does, parsing Rust code for no apparent reason doesn't make too much sense, both from a performance & a DX standpoint, so this is a great change

[Madoshakalaka]

LGTS, thanks for contributing