Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    M. Mert Yıldıran
    @mertyildiran
    @naltun please feel free to ask anything.
    Noah Altunian
    @naltun
    Hey @mertyildiran, can you try installing and running this when you get a chance? https://github.com/chaos-lang/fs
    Noah Altunian
    @naltun
    I have a symbol that I'm unable to be found when the library is imported. I'm using nm to help pinpoint it, but my eyes are glossing over the code at this point. I'll look again in the morning.
    M. Mert Yıldıran
    @mertyildiran
    Hi, nm would not help in this case. Since function is loaded dynamically. The issue was you removed function KaosRegister while forking the template and forgot to add it back. I've fixed this issue and made some additions/fixes here and there with this commit chaos-lang/fs@392236c
    @naltun there is an issue possibly related to file paths on Windows that I'm hoping to fix with chaos-lang/fs@a962203 blindly. If this does fix the issue then I'm gonna switch to Windows and try to understand the problem tonight. In case you've a Windows machine (or dual boot) then you can also do that if you want.
    M. Mert Yıldıran
    @mertyildiran
    and it didn't fix :smile:
    Noah Altunian
    @naltun
    Oh my. Well I'll reread this after work and see what I can try. 😁 I use a Mac for work and Linux for everything else. I'm also migrating away from the Mac soon, so I'll be full Linux again.
    It'll be good once we have Windows users/testers/contributors.
    M. Mert Yıldıran
    @mertyildiran
    OK then Windows is my part.
    Noah Altunian
    @naltun
    I just tried your changes after reviewing the commits. AWESOME.
    I learned a bit more about the Chaos API. Also, it was awesome to test my C changes 😁 first C code that I've ever contributed. I'm feeling pretty darn awesome right now. Also, the C API is not hard to grok. I feel like I'm already getting a bit cozy with it. More to learn and need to practice, of course, but you've implemented a very nice API.
    I've used the word 'awesome' 3 times, so I must be in a pretty good mood. Thanks for your help/feedback. I'll continue to review the code later on, and will write some more this evening.
    M. Mert Yıldıran
    @mertyildiran
    It really feels nice to hear these words. Thank you so much for your interest! I'll fix the reason of failures in CI on Windows now.
    M. Mert Yıldıran
    @mertyildiran
    By the way, I've fixed the issue on Windows with chaos-lang/fs@eceb601
    Noah Altunian
    @naltun
    Nice 👍.
    Noah Altunian
    @naltun
    Morning @mertyildiran. Question: do you prefer squash merging?
    Oh! It's the 1 year birthday of Chaos, correct?
    Noah Altunian
    @naltun

    Also, I'm sitting on this branch: https://github.com/chaos-lang/fs/tree/rename

    I don't want to merge it before I get a test in. How do we go about testing?

    Noah Altunian
    @naltun
    I also just had a thought: the new fs spell was supposed to be for filesystems, but it so far seems to only be manipulating files. Question: should we change this to the file or fileutils spell?
    Python has these modules for manipulating files/directories (paths):
    image.png
    And the fs spell seems to be a bit more of the os/sys Python modules. At least in intent.
    The fs API currently supports: read(), copy(), and soon-to-be rename(), all related to files.
    Thoughts?
    M. Mert Yıldıran
    @mertyildiran

    Morning @mertyildiran. Question: do you prefer squash merging?

    I prefer linear history with as little squash and merge commits as possible because of this email of Linus: https://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html

    If something really needs a squash then at list this method should be used: https://stackoverflow.com/a/5190323/2104879

    Oh! It's the 1 year birthday of Chaos, correct?

    I didn't know that today is the birthday of Chaos :smile: How did you determine that? Looked at the first ever commit?

    Also, I'm sitting on this branch: https://github.com/chaos-lang/fs/tree/rename

    I don't want to merge it before I get a test in. How do we go about testing?

    I expect to have tests for each functions in the library in https://github.com/chaos-lang/fs/blob/44329743f33953dcb51cb6a65f6b1deaad0f8f2c/test.kaos

    Noah Altunian
    @naltun

    :smile: How did you determine that?

    I saw your LinkedIn had the start-month of your volunteer on the project as Dec '19. I don't know the day, but the month? ; ) So this requires a big congrats, right?

    This message was deleted
    We're almost there: Dec 21, 2019 is the birthday of Chaos. And you know, that's a very good day for a birthday.
    M. Mert Yıldıran
    @mertyildiran
    Yeah, I've looked at the first ever commit and it's Date: Sat Dec 21 21:55:22 2019 +0300. But sure we can do an early celebration.
    Yep.
    Noah Altunian
    @naltun
    I think you saw my comments before I deleted them (before checking)
    hehe
    M. Mert Yıldıran
    @mertyildiran
    Yes :smile:
    Noah Altunian
    @naltun
    But this is cool. Dec 21
    This message was deleted
    M. Mert Yıldıran
    @mertyildiran

    I also just had a thought: the new fs spell was supposed to be for filesystems, but it so far seems to only be manipulating files. Question: should we change this to the file or fileutils spell?

    Python's modules related to file manipulation is a little bit messy. They've introduced more modules and kept the old modules along the way for the sake of backward compatibility. Since even the core modules requires separate installation procedure in Chaos, if we split the modules then it might become a little bit inconvenient to use them. I would go with a relatively big module that covers everything related to filesystem. fs is a good name for such a module I think.

    M. Mert Yıldıran
    @mertyildiran
    All core modules should hide/abstract OS-specific issues as much as possible so that users will not have to deal with them. We will still need an os module to retrieve operating system's kernel name/version and distro name/version etc. We can have modules like linux, windows and macos to provide OS-specific functionality if it's really needed.

    The fs API currently supports: read(), copy(), and soon-to-be rename(), all related to files.

    If rename() function is able to do more than just file renaming like changing the path then I think move() name is more suitable.

    Noah Altunian
    @naltun
    Great feedback.
    I'll consider this when adding/refactoring fs.
    M. Mert Yıldıran
    @mertyildiran
    I think we need fs.open() and fs.close() functions such that fs.open() returns the file pointer and we pass that file pointer to fs.read() and fs.write().
    But Chaos language does not have any built-in data type to store a file pointer or any pointer at all. We can return it as a string like str file_pointer = fs.open(some_path) but it would be a bad approach.
    I think instead we should introduce a new primitive data type named byte to the language and it will be prefixed with an integer like 1 byte, 2 byte etc. So that we can have the file pointer like 1 byte file_pointer = fs.open(some_path).
    M. Mert Yıldıran
    @mertyildiran
    On a second thought, prefixing it with an integer might introduce weird challenges in the implementation. Alternatively we can do: DD, DB, DW, DQ, DT just like how it's in Assembly. But I think 1 byte is cooler.
    Would you like to add such a data type into language's source?