Mirror of forum.nim-lang.org

5476 :: Why does nim put the Export marker on the right side?

[2019-11-08T05:05:44+01:00]

javinyang (orginal) [2019-11-08T05:05:44+01:00] view original
```
type
  MyType* = ref object
    a*: int32
    b*: int32
    c*: int32

proc myProc*() = discard
```
I don't understand why it is placed on the right side. Is there any reason for this design? Feel good on the left side.
```
type
  *MyType = ref object
    *a: int32
    *b: int32
    *c: int32

proc myProc*() = discard
```
And why is the following not allowed?
```
dumpTree:
  mytype MyType:
    a*: int
```
Error: expression expected, but found ':'

Araq (orginal) [2019-11-08T10:45:03+01:00] view original

I took it from Oberon after playing with an export keyword that never looked as nice. I never really considered a prefix operator as the name is more important and important things should come first. The visibility is mostly an annoying detail to me so it has to be as unobtrusive as possible. YMMV of course.

drkameleon (orginal) [2019-11-08T11:01:07+01:00] view original
I definitely agree. Variable visibility should be secondary. Not to mention that having it on the left side, just for SOME object fields for example, would make the whole thing ugly (at least for me):
```
type
  MyType = ref object
    a: int32
    *exported: int32
    not_exported: int32
```

cdome (orginal) [2019-11-08T13:32:31+01:00] view original

No difference at all guys. Moving it will achieve nothing.

I am not sure it was mentioned before I want this to be heated by Araq. I find export marker especially useful in the following way: I search a function name and I find too many result because it is used in too many places. I add export marker and I find exactly where the function is defined.

cantanima (orginal) [2019-11-09T15:59:04+01:00] view original
And why is the following not allowed?
```
dumpTree:
  mytype MyType:
    a*: int
```
I'm a bit perplexed that several people are saying this should be OK. Why should a type's field be visible outside a module if the type itself is not visible outside a module?