dqneo / minigo Goto Github PK

Currently, only single file is allowed in std (and other foreign) packages.
We need to improve it.

We should use gtype.getKind() instead.

as in the gc.

Currently, parser ignores directory parts in the import path.
So we cannot use a path like github.com/minigo/

To implement "go get" or to invoke assembler and linker

Realize this https://github.com/DQNEO/minigo/compare/pointer-arith?expand=1

Hi @DQNEO!

The mini Go compiler looks like a very interesting project. I wanted to take it out for a spin, but ran into the follow error when running go get:

u@x1 ~> go get github.com/DQNEO/minigo
# github.com/DQNEO/minigo
goget/src/github.com/DQNEO/minigo/main.go:106:54: undefined: internalRuntimeCode
goget/src/github.com/DQNEO/minigo/main.go:118:14: undefined: stdPkgs

Cheers,
Robin

Current Implementation is poor.

It's terrible now.
https://godoc.org/github.com/DQNEO/minigo

1. return an struct pointer in a function which returns an interface

I liked to have std packages as strings , mainly for portability.
By this design the compiled binary work in any directory without minigo source code.

But I think no one has cared about portability of minigo, and this leads to additional complexity by requiring special treatments for std packages.
I decide to change this design.

Separate assembly files like C

 for _, v := range []byte("foo")

This does not work yet.

Something like

assertNotReached(node.token())

c.f. https://webkit.org/blog/5397/a-guide-to-assertion-macros-in-webkit/

Currently, I'm afraid we cannot use interface of foreign (which means out of main) packages.

IrInterfaceMethodCall.emitMethodCall and IrStaticCall.emit should be DRYied.

Logic of passing various arguments to interface methods is broken.

System call (brk?) should be called.

an issue I found when I converted cstring to gostring around for labels.

http://man7.org/linux/man-pages/man2/getdents64.2.html#top_of_page

• Translate the togetter history.
• Add images

https://docs.google.com/document/d/1jPxOyCPyaQKESrkvu26aiDwXAoi3YDGPvoI3CJdNYms/edit#heading=h.ioacxcp3u0ow

It's waste of time.

Stop calling libc's printf

Currently, the dependency graph is hard coded in builder.go

We should do this automatically.