WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Symbols have hash codes that are stable between compiler runs. To find out what creates a Symbol, first find out its hash code, then simply print a stack trace in Symbol's constructor when the hash code matches. The stack trace will probably contain some new* methods in Symbols.scala.
When a symbol is created, its .info is set to a lazy type. This lazy type will later be used to actually calculate the .info for the symbol (see complete and doComplete in SymbolLoader). One way to debug information about the completion of the symbol is to print information when the symbol with the correct hash code is being completed.
Symbols have hash codes that are stable between compiler runs. To find out what creates a Symbol, first find out its hash code, then simply print a stack trace in Symbol's constructor when the hash code matches. The stack trace will probably contain some new* methods in Symbols.scala.
When a symbol is created, its .info is set to a lazy type. This lazy type will later be used to actually calculate the .info for the symbol (see complete and doComplete in SymbolLoader). One way to debug information about the completion of the symbol is to print information when the symbol with the correct hash code is being completed.
Right, hashCode for a symbol delegates to id, which is shorter to type :). And you can get the compiler to append symbol ids in its pretty-printed output using -uniqid
then simply print a stack trace
Which can be done using Thread.dumpStack
debug information about the completion of the symbol
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Symbols have hash codes that are stable between compiler runs. To find out what creates aSymbol, first find out its hash code, then simply print a stack trace inSymbol's constructor when the hash code matches. The stack trace will probably contain some new* methods in Symbols.scala.When a symbol is created, its
.infois set to a lazy type. This lazy type will later be used to actually calculate the.infofor the symbol (seecompleteanddoCompletein SymbolLoader). One way to debug information about the completion of the symbol is to print information when the symbol with the correct hash code is being completed.