How to understand that "calling get arguably breaks referential transparency"? on page 99?

[Dahui]

On chapter 7, page 99, it says that "But if unit begins evaluating its argument concurrently, then calling get arguably breaks referential transparency.". 

I can't figure out what is the RT here? Could anyone help to explain it? Thanks.

[Raymond Tay]

Hi Dahui,

From that chapter's context, i believe what is meant here given that "def unit[A](a: => A)" is defined, is that we generally have no idea what the type parameter "A" represents - infact it could be anything e.g. closures over vars or some side-effects etc and the authors go to explain how in the code snippet in that same page i.e. page 99.

On Wed, May 30, 2018 at 10:55 AM Dahui <dhy...@gmail.com> wrote:

On chapter 7, page 99, it says that "But if unit begins evaluating its argument concurrently, then calling get arguably breaks referential transparency.". 

I can't figure out what is the RT here? Could anyone help to explain it? Thanks.

--
You received this message because you are subscribed to the Google Groups "scala-functional" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-function...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

http://about.me/rayt

[Dahui]

Thanks! 

I found another reply which explained very good.  

https://groups.google.com/d/msg/scala-functional/7o4_ZRJEoQA/kNBZmM_HG4EJ

在 2018年5月30日星期三 UTC+8上午11:20:47，raymondtay1974写道：

[Raymond Tay]

Glad to hear that.