There is VecInit.tabulate, why not VecInit.fill?

[mwachs5]

Type of issue: feature request

Impact: API addition (no impact on existing code)

Development Phase: request

Other information

It looks like there is a VecInit.tabulate. But there isn't a VecInit.fill. This seems asymmetrical.
There is VecINit(Seq.fill(...) {...}) but this is more verbose. Why should there be one and not the other?

https://www.chisel-lang.org/api/latest/chisel3/VecInit$.html#tabulate[T%3C:chisel3.Data](n:Int)(gen:Int=%3ET):chisel3.Vec[T]

If the current behavior is a bug, please provide the steps to reproduce the problem:

What is the current behavior?

There is only VecInit.tabulate, so you have to do somethign like VecInit.tabulate(num){unused => false.b})

What is the expected behavior?

That one could call VecInit.fill(num){false.b}

Please tell us about your environment:

What is the use case for changing the behavior?

more consistent, intuitive API

[jackkoenig]

Yeah this is an oversight. Since Vec extends Seq, perhaps we should have VecInit extend SeqFactory (https://www.scala-lang.org/api/2.12.10/scala/collection/generic/SeqFactory.html) This would give us all of the expected constructors. That would require fixing #1354 as well.

[mwachs5]

Closed by #2059 , thanks @anniej-sifive !