There are a few I’m aware of:
- Rust-style
use(multiple imports per statement, renaming items usingas) - Java-style
import(single import per statement, no renaming (afaik)) - Zig-style
let xlib =(imports as assignments) - C-style
(no importing, just pastes the code of the named file)
I think C# handles this pretty well. You include namespaces with whatever granularity you need, down to a single class (or interface or whatever) and can alias them.
using MyProject.Domian.Entities; //the whole module using Routes = MyProject.Api.Contract.Routes.Http; //an aliased single classI bet Java had this too, C# us still mostly Java: Microsoft Edition.
It’s actually pretty similar to rust, only that rust can import multiple modules (namespaces) in one line, which is just syntax sugar, and the syntax is slightly different.
Your example would be
use my_projext::domain::entities; use my_project::api::contracts::routes::http as routes;Rust adds the curly brace syntax so you can import a specific subset from a module, but I can’t decide if I like that. In C# you just keep adding extra lines which take up more vertical space, but if you sort your using a alphabetically (which your IDE can do), I think you get a very readable list. In sum, Rust adds a feature that I don’t really actually like.
c# is delphi with some realized mfc lofty goals.
first, microsoft liked delphi and hired the guy who created delphi to create c#
second if you read an mfc book from the 90s that talks about history and goals, 6ou can see they wanted the .net framework
You know, I don’t know enough about Delphi. I’ve great good things, I should check it out, I guess it might be familiar.
I like Rust’s style. It’s simple and it does everything you need. As much as I love Elixir, which I write at my day job, it has alias, import, use, and require, which each import things different, and it can get a bit confusing.
In order or preference, out of the ones I’m familiar with:
- Java. Very simple. Diff friendly. Import names match the filesystem.
- Rust. Also good - you can do it diff friendly though nobody does. Slightly confusing distinction between module hierarchy and filesystem.
- Python. Pretty bad. Conflates third party packages with local files, almost nobody actually understands relative imports, even more confusing distinction between module hierarchy and filesystem. Module imports can have side effects. Unnecessarily different syntax between
import...andfrom .... import.... - C/C++. Obviously this is the worst.
Well, I have been using python for a long time and was ready to disagree with you but damn, it really do be like that.
I suspect most developers have a “favorite language” and are just going to respond with “the import style my favorite language uses”.
I would never classify Python as my favorite language, but I really like the import system.
Elm:
-- Import under the name "List" import List -- Import aliased under the name "JD" import Json.Decode as JD -- Import Html, and put the Html type into the unqualified namespace import Html exposing (Html) -- Import Http, and put everything from it in the unqualified namespace import Http exposing (..)I’m most used to c style and as a result I like it because it’s simple and uncomplicated. I recently started learning rust and quite like their way of doing it, although there’s also mod and I haven’t quite figured out when to use which. I just do what rust analyser tells me :)
useimports things (items, crates, modules), whilemoddefines a module (either in another file with a a semicolon or in the same file with curly braces)Cheers
I like being able to import multiple things from a given package/module on the same line. Aliasing is also very useful.
Like to import via smuggli- OH we’re talking about coding? Uhh Java does it pretty well and we’re learning C# rn so gonna have to learn how to import that soon
Zig and Rust are good. Java is painful.
But the best for me is Clojure:
(require [my.module :refer [func1 func2]] [Some.lib :as lib])I’m not educated enough to have an opinion that goes beyond what I like to type. I find C style to be the nicest.
Python’s work great.
Short, clear and flexible.
someone above listed exactly why Python’s is so bad. it’s pretty bad compared to most other solutions, even ruby’s, which isn’t as good as modern solutions.
I saw a few personal opinions with no real substance.
Module resolution is a pretty solid reason as to why it’s bad.




