When I started reading about Ownership, I was thinking

I have done C. I understand memory

But Rust book explains :

If you are familiar with systems programming, you might think of memory at a low level like “memory is an array of bytes” or “memory is the pointers I get back from malloc”. .. The low-level model is too concrete to explain how Rust works. Rust does not allow you to interpret memory as an array of bytes, for instance.

I wrote about logseq almost two years ago and then I think when I switched job, I stopped using logseq.

When I updated macOS, I forgot to install it, and forgot about it overall (I started using denote - in Emacs for some time)

Recently when I started using obsidian while trying l learn more about it, I came across logseq again.

I tried it again (after 2 years)

I spent time learning basics (again)

Yesterday, I was trying to access Bard API via Rust

The task is WIP because :

1. I’m still learning Rust (Although on Day 5 I was able to access a URL from rust code)
2. I didn’t know how to access Bard API

It started with a Youtube video that:

• Uses python code which uses Bard library
  • Not sure if it is official one or third party one
  • In either case it won’t be directly useful in rust code
• Uses a hack to get session cookie from browser (which will expire sooner or later)

At that time, I didn’t know whether Google has made Bard API accessible via an API

I want to access Bard API via Rust, but it will take some time.

Here are the things I did today.

First, I tried (successfully) to access an URL via Rust code. ✅

I used the reqwest module.

I just added this dependency in my Cargo.toml and (like in other languages) the dependency hell was let loose 😄

67 other modules were added to the Cargo.lock!

I also learnt to use global variables in Rust.

Started with (optional) assignment at the end of “Programming Concept” chapter : Convert temperature between Celsius and Fahreinheit. ¹

Since the algorithm itself is not part of the learning the language, I asked Google Bard about the formula.

It was nice working on some code after a while (Aside from work, I mean)

Once again, I realized that compiler is very helpful 😍

I started simple.

Breaking down functionality into smaller functions. (Makes me think of unit testing them. Note to self : Read up about unit testing in rust)

Today I finished Functions and Control Flow etc.

While these are not new “concepts” for me, one always learns something new when learning a new language.

Two things I learnt:

1. I liked the fact that rust does not evaluate anything other than boolean as truthy like both python and ruby
2. loop can have labels, and can be used with break and continue to indicate where should the execution continue

Today I started with Data Types

While most of it is intuitive, it is useful to go over the documentation.

e.g. For tuple, I had expected that to access specific index, syntax would be mytuple[0]. mytuple.0 was not I had expected.

I also tried to print the tuple.

In the process, I learnt about pretty printing only from the compiler errors.

The compiler errors are so descriptive 😍

Here is the code in case you are interested

Today I finished the Number guessing game

During the early part of the code, my mind started thinking “How will comparing string input from the user, work with a number? 🤔” (💪 of having gone through such issues numerous times over the years)

Of course, it was explained later.

I was a bit disappointed that the code paniced upon entering non-number 😞 especially after the expect clause.

Turns out that is expected behaviour.

In this new year, I have decided to learn rust

All my recent experience has been in dynamic languages (90% python, 10% ruby)

But I started my software development career in C, and did that for probably 10 years. So I’m not new to compiled languages.¹ But things have changed a lot (for the better) in these years.

Additionally, rust is getting a lot of attention from bigwigs like MS.