From fc4b9e1f188d99770cfc7d8a2553cd83b59a6684 Mon Sep 17 00:00:00 2001 From: Liin207 Date: Mon, 3 Apr 2023 10:07:23 +0700 Subject: [PATCH 1/2] messages --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 68299b7a..0b051ff8 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ Lack of eager execution was one of the main complaints against TensorFlow. We al With TensorFlow 2.0, eager execution is activated by default and the very cool thing is that the code nearly doesn't change. Under the hood, you are just working with so-called "EagerTensors" instead of "Tensors" but since they share the same interface, the difference is barely noticeable. Even in execution speed, the difference is hard to see. -This means, from now on, TensorFlow code can be used and debugged as ordinary python code (using numpy for example). This is one aspect of making TensorFlow more pythonic. +This means from now on, TensorFlow code can be used and debugged as ordinary python code (using numpy for example). This is one aspect of making TensorFlow more pythonic. Below there are two tasks. I highly recommend doing them because while watching me coding and coding yourself you'll definitely internalize the material. From 6413eda54a918c50abc98791929a230e9d8505ce Mon Sep 17 00:00:00 2001 From: Liin207 Date: Mon, 3 Apr 2023 10:15:42 +0700 Subject: [PATCH 2/2] grammar check --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0b051ff8..79db94c7 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ The following are all the changes coming in TensorFlow 2.x. Let's have a closer ## Eager Execution -Lack of eager execution was one of the main complaints against TensorFlow. We all can relate. Having to execute the whole graph and then trying to debug based on the errors was very tedious. Especially, since values of intermediate results haven't been accessible without printing them out by mixing in debug statements into the production code. +Lack of eager execution was one of the main complaints against TensorFlow. We all can relate. Having to execute the whole graph and then trying to debug based on the errors were very tedious. Especially, since values of intermediate results haven't been accessible without printing them out by mixing in debug statements into the production code. With TensorFlow 2.0, eager execution is activated by default and the very cool thing is that the code nearly doesn't change. Under the hood, you are just working with so-called "EagerTensors" instead of "Tensors" but since they share the same interface, the difference is barely noticeable. Even in execution speed, the difference is hard to see.