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
Avoid misleading special characters within lambda synthetic class names
Enough code in cbmc and its users relies on method names having the form
'java::package.Class.method:(type)' that the existing method for synthesising
lambda class names, which could yield things like java::synthetic_lambda$main:()V$0.<init>,
could cause problems when that colon character in the middle of the name was mistaken
for the function name's trailing type information. Similarly we might end up
needing to append fake type information to the <init> and apply symbol names to
appear "normal" enough.
0 commit comments