3 ms·

Almost like the way D programming language handle it http://dlang.org/module.html http://dlang.org/module.html

• kibwen 14y ago
  For completeness, here's how Rust handles modules: http://dl.rust-lang.org/doc/tutorial.html#modules-and-crates http://dl.rust-lang.org/doc/tutorial.html#modules-and-crates Browsed golang.org for a bit and didn't find any info on how Go handles modules/packages. All I know is that it has something to do with the folder hierarchy of your project (links appreciated).
  • ori_b 14y ago
    in Go, you declare a package for your file. Exported symbols start with an upper case letter.
    • kibwen 14y ago
      Okay, so the `package` keyword in Go is like the `export` keyword in this proposal? Does Go allow submodules?
      • strmpnk 14y ago
        Packages are given paths or URLs so they might be a subpath but it's not really a subpackage of any sort other than by name.
      • deleted 14y ago
        [deleted]
  • enneff 14y ago
    Here's a talk I gave about Go's package system: http://nf.id.au/my-linuxconfau-go-talk-mostly-about-packages http://nf.id.au/my-linuxconfau-go-talk-mostly-about-packages
• acomjean 14y ago
  also looks like ada to me with Ada.Strings.Unbounded; but "withing" ada, you'd get the parent package(s). eg you'd get Ada.Strings and Ada.Strings.Unbounded but not Ada.Strings.Fixed
• CountHackulus 14y ago
  When I saw import std.stdio; I could've sword I was looking at D for a second. So clearly I'm all for this proposal. Anything to make C++ more like D is a win in my books.