---
title: "Comment by sammo90 on \"Synchronisation and Concurrent Access in Cats Effect 3 [Part 7]\" | Hashnode"
description: "Wouldn't it be better to use _ &lt;- IO.println(... instead of _ = println( ... ?"
url: "https://hashnode.com/posts/synchronisation-and-concurrent-access-in-cats-effect-3-part-7/628eab0143220290a7eeb6da/comment/6a0705ceb54b0a065f49b586"
---

[Discussion](https://hashnode.com/posts/synchronisation-and-concurrent-access-in-cats-effect-3-part-7/628eab0143220290a7eeb6da)

Comment [Synchronisation and Concurrent Access in Cats Effect 3 \[Part 7\]](https://hashnode.com/posts/synchronisation-and-concurrent-access-in-cats-effect-3-part-7/628eab0143220290a7eeb6da)

[sammo90](https://hashnode.com/@sammo90)

[May 15](https://hashnode.com/posts/synchronisation-and-concurrent-access-in-cats-effect-3-part-7/628eab0143220290a7eeb6da/comment/6a0705ceb54b0a065f49b586)

Wouldn't it be better to use

```
_  <- IO.println(...
```

instead of

```
_ = println( ...
```

?

[Yadukrishnan](https://hashnode.com/@yadukrishnan)

[May 15](https://hashnode.com/posts/synchronisation-and-concurrent-access-in-cats-effect-3-part-7/628eab0143220290a7eeb6da/comment/6a0705ceb54b0a065f49b586#reply-6a0735bb73afc887577b7763)

Yes, definitely it is better to use it that way to be more functional. I updated it.
