sun ao

+1 Same issue

@skys215 好的 感谢分享~看反编译看的脑壳痛...

I am also interested in this feature Cause sometimes we don't that want something 'XXX-hover' in the path since it is pretty hard to record the 'hover' event..

@lethefrost hi according [here](https://github.com/ExodiusStudios/vscode-comment-anchors/blob/f78b37dc41ce1df86f9782288c6fea2e19e89804/src/anchorEngine.ts#L328) it is seem to be intended Maybe we can create a new parameter for this feature

@lethefrost Hi, my bad. Is setting **Match case** to **false** can do the trick for you ? 

Currently you can use some tricks mentioned in #39

#17 related

@trevorstephens A reference may be helpful ... https://github.com/DEAP/deap/blob/f6accf730555c5bbc1c50ac310250ad707353080/deap/gp.py#L891-L914 It seems like that they just replace the one violates the max depth constraint with a new random one

+1

@ganesh3 hi have you solved this problem?