Arc Forum | "The reason I left off the leading 0s is that some languages (like Racket) let y...

Arc Forum

1 point by rocketnia 4529 days ago | link | parent

"The reason I left off the leading 0s is that some languages (like Racket) let you do that."

Hmm, I thought JavaScript was like that too, but it appears ECMAScript 5 doesn't allow it, and Chrome's implementation doesn't like it either.

---

"Well, I usually end up putting a lot of changes into a single commit, so just reading the diffs should be enough?"

There were lots and lots of indentation-only changes. If those were separated into their own commits, with commit messages that indicated that the indentation was all that changed, it would have been easier.

I trust you to know that ultimately, it doesn't matter what's easy for me as long as it's easy for you. :-p

---

"Nuit hasn't changed very much from when I first posted it[...]"

The wordings changed. Even if you had commit messages that stated your intentions like this, I would have looked at the changes carefully in case something became contradictory or ambiguous by accident.

In hindsight, I should have just checked out the old and new versions of the project and done a diff, lol.

Don't trust me to go to this effort all the time, but I guess I was in the mood for it.

---

"Oh! And the second part of the @ list can now be any arbitrary sigil rather than just a string."

That was the most significant change, in my mind. This example of yours should be a good test case for Nuit implementations:

  Nuit  @foo @bar qux
               yes nou
          corge
          @maybe
            @
            someday
  JSON  ["foo", ["bar", "qux", "yes nou"] "corge" ["maybe", [], "someday"]]

---

"I've been mulling over the idea of getting rid of the \ sigil..."

I've been wondering about that too. It seems like " or ` will work just as well for those cases.

1 point by Pauan 4529 days ago | link

"There were lots and lots of indentation-only changes. If those were separated into their own commits, with commit messages that indicated that the indentation was all that changed, it would have been easier."

Sure, but that woulda been more work for me. :P I honestly wasn't expecting you to pore through the commit log... Since I am used to working alone, I just use git as essentially a safety net: it lets me go back to an old version just in case the new version doesn't work out. So commit messages aren't nearly as important to me as they would be in a team-based environment.

---

"The wordings changed. Even if you had commit messages that stated your intentions like this, I would have looked at the changes carefully in case something became contradictory or ambiguous by accident."

Then the commit messages would have been useless anyways, right? :P

---

"In hindsight, I should have just checked out the old and new versions of the project and done a diff, lol."

Github even lets you do a diff on their website! :D

---

"Don't trust me to go to this effort all the time, but I guess I was in the mood for it."

I honestly wasn't expecting anything like that.

---

"That was the most significant change, in my mind. This example of yours should be a good test case for Nuit implementations:"

Check out "nuit-test.arc" which should have conformance tests for everything in the Nuit spec:

https://github.com/Pauan/ar/blob/arc/nu/lib/nuit/nuit-test.a...

---

"I've been wondering about that too. It seems like " or ` will work just as well for those cases."

Yeah, I know. I guess it's because the only single-line thing is a non-sigil, and I wanted to be able to slap anything in without worrying about it, so \ was a single-line escape thingy. But I think I can safely get rid of it.

-----