garble

Author	SHA1	Message	Date
Daniel Martí	b8aec97e86	don't garble any embedded fields In the added test case, we'd see a failure, since we garbled the name of the "Embedded" type but not its use as an anonymous field. Garble both. This might possibly break some reflect code, but it doesn't seem like we have an option. When we garble a type, it's impossible to tell if it's going to be used as an anonymous field later. Updates #9.	6 years ago
Daniel Martí	1ce5310440	don't garble exported struct fields They might reasonably affect the behavior of the code, such as when encoding/json is used without tags.	6 years ago
Daniel Martí	5ccf56662a	don't panic with struct pointer anonymous fields While at it, make the "object of type" code shared and more robust.	6 years ago
Daniel Martí	63cbc01628	support anonymous fields better	6 years ago
Daniel Martí	aba66758ca	support type switches with symbolic vars	6 years ago