Skip to content

cache poisoning for "enum after enum" case #8

@DronCode

Description

@DronCode

Test case:

namespace engine::render
{
	/**
	 * @runtime
	 */
	enum class ESample
	{
		ES_FIRST = 1,
		ES_SECOND = 2
	};
}

enum ESomeLegacy
{
	__LDO_NO_INIT_OR_SMTH_I_DONT_KNOW__ = 0x1337,
	_SOME_WEIRD_ENTRY = 0x201,
	LOL_IT_MUST_BE_SOMEWHERE_ELSE = 0x500
};

Expected result: enum engine::render::ESample has 2 entries
Actual result: enum engine::render::ESample has 5 entries (imported entries from ESomeLegacy)

It's critical issue, will release a new version soon.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions