fix(compiler-core): avoid using component name as parameter name

[linzhe141]

close #11730
this pr -- playground v-for case
this pr -- playground v-slot case

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	100 kB	37.7 kB	33.9 kB
vue.global.prod.js	159 kB	57.5 kB (+4 B)	51.1 kB (+6 B)

Usages

Name	Size	Gzip	Brotli
createApp	55.1 kB	21.2 kB	19.3 kB
createSSRApp	59.1 kB	22.9 kB	20.8 kB
defineCustomElement	59.8 kB	22.7 kB	20.7 kB
overall	68.8 kB	26.3 kB	23.9 kB

[pkg-pr-new]

commit: bbea42f

@vue/compiler-core

pnpm add https://pkg.pr.new/@vue/compiler-core@11731

@vue/compiler-dom

pnpm add https://pkg.pr.new/@vue/compiler-dom@11731

@vue/compiler-sfc

pnpm add https://pkg.pr.new/@vue/compiler-sfc@11731

@vue/compiler-ssr

pnpm add https://pkg.pr.new/@vue/compiler-ssr@11731

@vue/reactivity

pnpm add https://pkg.pr.new/@vue/reactivity@11731

@vue/runtime-core

pnpm add https://pkg.pr.new/@vue/runtime-core@11731

@vue/runtime-dom

pnpm add https://pkg.pr.new/@vue/runtime-dom@11731

@vue/server-renderer

pnpm add https://pkg.pr.new/@vue/server-renderer@11731

@vue/shared

pnpm add https://pkg.pr.new/@vue/shared@11731

vue

pnpm add https://pkg.pr.new/vue@11731

@vue/compat

pnpm add https://pkg.pr.new/@vue/compat@11731

Open in Stackblitz

[edison1105]

the cause is here

core/packages/compiler-core/src/transforms/transformElement.ts

Lines 345 to 351 in 741d8a0

	checkType(BindingTypes.LITERAL_CONST)
	if (fromConst) {
	return context.inline
	? // in inline mode, const setup bindings (e.g. imports) can be used as-is
	fromConst
	: `$setup[${JSON.stringify(fromConst)}]`
	}

[linzhe141]

the cause is here

https://github.com/vuejs/core/blob/741d8a0710e08c925da2511ce764aa87c4a291d9/packages/compiler-core/src/transforms/transformElement.ts#L345-In

this case, throwing an error might be more reasonable？

[edison1105]

This check is not correct. Consider the following scenario:

  <div v-for="Comp of list">
    <Comp>{{Comp}}</Comp>
  </div>

Playground

[edison1105]

the cause is here
741d8a0/packages/compiler-core/src/transforms/transformElement.ts#L345-In

this case, throwing an error might be more reasonable？

I think so

[edison1105]

Consider this scenario

[linzhe141]

Consider this scenario

Yeah, there are some other scenarios besides v-for that I didn't consider.