Rebase wrapper #332
|
|
@ -171,7 +171,7 @@ func (rebase *Rebase) Abort() error {
|
|||
|
|
||||
//Free frees the Rebase object and underlying git_rebase C pointer.
|
||||
func (rebase *Rebase) Free() {
|
||||
runtime.SetFinalizer(rebase, nil)
|
||||
C.git_reference_free(rebase.ptr)
|
||||
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it. This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
We have prior art of naming We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
Like with the init function, this should be called Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
This return value does not match how Go reports errors. I would expect a This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
There is no There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
There is no There is no `git_rebase_next` in git2go, we have `Next()`.
Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there. Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
The other public id fields are named The other public id fields are named `Id`.
Ok, I followed go convention suggested by my IDE plugin Ok, I followed go convention suggested by my IDE plugin
Done Done
Done Done
Done Done
Done. Done.
I also added `ErrClassRebase` in `git.go`
Hope this is correct
Done Done
Done Done
|
||||
C.git_rebase_free(rebase.ptr)
|
||||
|
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it. This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
We have prior art of naming We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
Like with the init function, this should be called Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
This return value does not match how Go reports errors. I would expect a This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
There is no There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
There is no There is no `git_rebase_next` in git2go, we have `Next()`.
Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there. Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
The other public id fields are named The other public id fields are named `Id`.
Ok, I followed go convention suggested by my IDE plugin Ok, I followed go convention suggested by my IDE plugin
Done Done
Done Done
Done Done
Done. Done.
I also added `ErrClassRebase` in `git.go`
Hope this is correct
Done Done
Done Done
|
||||
}
|
||||
|
||||
func newRebaseFromC(ptr *C.git_rebase) *Rebase {
|
||||
|
|
|
|||
|
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it. This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it. This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
We have prior art of naming We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
We have prior art of naming We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
Like with the init function, this should be called Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
Like with the init function, this should be called Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
This return value does not match how Go reports errors. I would expect a This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
This return value does not match how Go reports errors. I would expect a This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
There is no There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
There is no There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
There is no There is no `git_rebase_next` in git2go, we have `Next()`.
There is no There is no `git_rebase_next` in git2go, we have `Next()`.
Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there. Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there. Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
The other public id fields are named The other public id fields are named `Id`.
The other public id fields are named The other public id fields are named `Id`.
Ok, I followed go convention suggested by my IDE plugin Ok, I followed go convention suggested by my IDE plugin
Ok, I followed go convention suggested by my IDE plugin Ok, I followed go convention suggested by my IDE plugin
Done Done
Done Done
Done Done
Done Done
Done Done
Done Done
Done. Done.
I also added `ErrClassRebase` in `git.go`
Hope this is correct
Done. Done.
I also added `ErrClassRebase` in `git.go`
Hope this is correct
Done Done
Done Done
Done Done
Done Done
|
||||
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
We have prior art of naming
git_repository_init()asInitRepository()since the namespacing in C and Go is bit different, so this should be calledInitRebase().We have prior art of naming
git_repository_init()asInitRepository()since the namespacing in C and Go is bit different, so this should be calledInitRebase().Like with the init function, this should be called
OpenRebase(). The documentation shouldn't reference the C functiongit_rebase_initbut our own.Like with the init function, this should be called
OpenRebase(). The documentation shouldn't reference the C functiongit_rebase_initbut our own.This return value does not match how Go reports errors. I would expect a
uintto return the current operation and anerrorto return any errors.This return value does not match how Go reports errors. I would expect a
uintto return the current operation and anerrorto return any errors.There is no
GIT_REBASE_OPERATION_EXECin git2go, it'sRebaseOperationExec.There is no
GIT_REBASE_OPERATION_EXECin git2go, it'sRebaseOperationExec.There is no
git_rebase_nextin git2go, we haveNext().There is no
git_rebase_nextin git2go, we haveNext().Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
The other public id fields are named
Id.The other public id fields are named
Id.Ok, I followed go convention suggested by my IDE plugin
Ok, I followed go convention suggested by my IDE plugin
Done
Done
Done
Done
Done
Done
Done.
I also added
ErrClassRebaseingit.goHope this is correct
Done.
I also added
ErrClassRebaseingit.goHope this is correct
Done
Done
Done
Done