tree ab9885e8f474fdca47c7c17d4711c80bdf34abcb
parent c9528fc6f66dfa732e54d6c6cfd258c29ddc134f
author Nate Bosch <nbosch1@gmail.com> 1578000940 -0800
committer GitHub <noreply@github.com> 1578000940 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeDmIsCRBK7hj4Ov3rIwAAdHIIAGbNDUu491cZvQo97EcraBra
 ewTV9jwEBao4wANLJHWmnN5ZKyh8t/y6Uv7i53JzpbtZUKf9Ky7vLWi4W6Km7Dob
 Y24P6DMYDUZSCMReQh8nKNimP4SVFUwKAuuQ9Rav5AZbtgO1mnFu+zu0xHtvSAJK
 +CLoQD62sWvNHL+sRz1oXyip2s+yl/h3EOMStc50giPl0ftaUilk+6dTyhDPaqQi
 NDXI2Z9NZw6R4hkfmx/d4htqFuLGs1EH7TwcWjVkDEYFpDSdoD9m1FV96HBlDhqN
 owA+ctZfj+gn7u5g/ByyPaPH4iZTXwlzkhOzfNeCT9daXbPUnZVNEdOeSwwJvt0=
 =lRAj
 -----END PGP SIGNATURE-----
 

Use explicit dynamic over void return types (#99)

Some implementations are relying on passing values through the visit
methods. Make return types explicitly `dynamic` to match their implicit
types from before.

This highlights that extending the `Visitor` class and expecting to return
useful values is inherently risky. Not only will usages fall through to dynamic
and have no static errors for things like typos, there are also places where
the values will be silently discarded by the implementation in` Visitor`.