What's with all the dead code in the Visual Scripting package?

Unity Engine
,
1

I’m reading the source code of the package (version 1.7.6), and:

  • IBranchUnit and IMultiInputUnit are defined on some units, but there is no code that actually uses them
  • ExpectedTypeAttribute is not used anywhere at all
  • (I will add to this list if I find more)

What’s going on?

2

IBranchUnit is used by [TypeIcon(typeof(IBranchUnit))] in SwitchOnEnum.cs and SwitchUnit.cs
IMultiInputUnit is used in MultiInputUnitAlphabeticDescriptor

3

Hi, thank you for your feedback. As you may know, Visual Scripting is an acquisition (previously called Bolt). And while we are developing new features, fixing bugs and preparing the future of VS we also have tasks to cover the codebase by tests (as there was no unit tests in Bolt) and removing dead/legacy code. It is just that there are not the priority. But don’t be scared, we know that those cleaning tasks need to be done and those are planned, we already do some at each sprints. But it takes time and as VS is intensively using reflection, even for is own codebase not just to get Unity API at runtime, we need to be careful when cleaning our codebase so as to keep things stable.