0000049: Computed struct name lookup should be smarter

ID	Project	Category	View Status	Date Submitted	Last Update

0000049	LDMud 3.3	LPC Compiler/Preprocessor	public	2004-04-13 22:35	2019-08-29 23:41

Reporter	~~lars~~	Assigned To	Gnomi
Priority	normal	Severity	feature	Reproducibility	always
Status	closed	Resolution	won't fix

Summary	0000049: Computed struct name lookup should be smarter
Description	Assume: struct Door { int flags; }; struct Exit { int flags; }; struct Room { struct Exit north; struct Exit south; }; struct Room room; string dir; room->(dir)->flags; This line throws a compiler error that 'flags' is defined in multiple structs (Door and Exit), even though the compiler could deduce that Exit is meant - because Room doesn't have any top-level Door members. Instead, the compiler currently considers all structs defined in scope as possible candidates. Testcase: t-040413
Tags	No tags attached.

Date Modified	Username	Field	Change
2004-04-13 22:35	~~lars~~	New Issue
2019-08-29 23:39	Gnomi	Relationship added	related to 0000843
2019-08-29 23:41	Gnomi	Assigned To	=> Gnomi
2019-08-29 23:41	Gnomi	Status	new => closed
2019-08-29 23:41	Gnomi	Resolution	open => won't fix
2019-08-29 23:41	Gnomi	Note Added: 0002478

Gnomi 2019-08-29 23:41 manager ~0002478	Actually it is not true, that the compiler can deduce the type of a runtime struct member lookup. The given struct can be a derived struct type containing additional members with different types, that the runtime lookup should find.