viper-admin

> **@fabiopakk** on 2018-10-17 15:08: > * changed the assignee from **@fabiopakk** to (none)

> **@fabiopakk** on 2018-10-17 15:15: > * changed the assignee from (none) to **@fabiopakk**

> **@fabiopakk** on 2018-10-17 15:28: > * changed the assignee from **@fabiopakk** to (none)

> **@fabiopakk** commented on 2019-05-20 09:09 `in` can either be parsed as a set operation or as part of a `let`, `unfolding` or `applying` expression in Viper. The rule for...

> **@fabiopakk** on 2019-05-20 09:09: > * changed the assignee from (none) to bitbucket user **krantikiran**

> **@fabiopakk** commented on 2019-07-31 09:29 Although good progress was made in branch [krantikiran\_issue\_216\_bactrack\_after\_in](https://bitbucket.org/viperproject/silver/branch/krantikiran_issue_216_bactrack_after_in), no solution that is general enough was reached yet, as we cannot limit expressions to proper...

> **@fabiopakk** on 2019-07-31 09:29: > * changed the assignee from bitbucket user **krantikiran** to (none)

> **@mschwerhoff** on 2018-08-26 09:53: > * changed `kind` from `proposal` to `enhancement`

> **@alexanderjsummers** commented on 2018-09-13 11:28 Summarising what I said yesterday, I'd be in favour of being able to differentiate "coincidences" in the AST notion of equality, such as occurrences...

> **@fabiopakk** commented on 2019-04-10 09:16 This is related with .