add marshal test suite

[illia-li]

No description provided.

[dkropachev]

	serialization.Set{
		Data:   []byte("\x00\x00"),
		Values: mod.IntoRef.Append("0"),
	}.Run("[0000]str", t, marshal, unmarshal)

In my opinion, it will be easier and clearer this way. And Set.Run function become easier and clearer.

Sure, let's do this then:

 	serialization.Set{
 		Data:   []byte("\x00\x00"),
 		Values: mod.AddVariants([]interface{}{"0"}, mod.IntoRef),
 	}.Run("[0000]str", t, marshal, unmarshal)

[illia-li]

Changes for serialization.Set was pushed, please check it for further work on the rest of the.

[illia-li]

Please check it out, if everything is fine, I will squash the commits and continue working on test suite for the corrupt cases

[dkropachev]

Bunch of small nit picks, last pack.
@sylwiaszunejko , can you please also take a look.

[sylwiaszunejko]

not related to the code, but please squash commits, so they are sets of distinctive changes not "resolve conversation" ones

[sylwiaszunejko]

I unresolved two comments that I don't think were addressed, but maybe I am missing something there are a lot of changes

[illia-li]

not related to the code, but please squash commits, so they are sets of distinctive changes not "resolve conversation" ones

I did it, divided by packages.
There were a lot of changes and the code changed first one way, then the other, in such a situation it is very difficult to do something differently

I unresolved two comments that I don't think were addressed, but maybe I am missing something there are a lot of changes

Fixed

[sylwiaszunejko]

Thanks for addressing the comments! I would like you to fix the commit history a little bit, commits like "cleaning", "optimizing x", "simplify x" should not exist, squash them and make the first commits clean/optimal/simple etc. in the first place. Having such commits with fixes that could be incorporated into the original commits is not something we want to merge into our git history

[illia-li]

Thanks for addressing the comments! I would like you to fix the commit history a little bit, commits like "cleaning", "optimizing x", "simplify x" should not exist, squash them and make the first commits clean/optimal/simple etc. in the first place. Having such commits with fixes that could be incorporated into the original commits is not something we want to merge into our git history

Something like this?

[sylwiaszunejko]

Right now, it's a single large commit. Ideally, it would be better to break it into smaller commits, but not in the way it was before, like "adding A" and then "optimizing part x of A." Instead, it should be more like "adding a" and then "adding b (not related to a)". For example, in this PR (#256), each commit focuses on adding or fixing one specific thing. If a commit is fixing something, it's from the master branch or was added before that PR, not something introduced in the same PR. Does that make sense?

[dkropachev]

Very last nits.
Let's also wait till @sylwiaszunejko approve it.

[dkropachev]

Let's move this code into utils package.

[dkropachev]

Last optimization,

Suggested change

	BrokenMarshalTypes []interface{}
	BrokenUnmarshalTypes []interface{}
	BrokenMarshalTypes []reflect.Type
	BrokenUnmarshalTypes []reflect.Type

[dkropachev]

Since reflect.Type is comparable, please replace it with reflect.TypeOf(val1) == reflect.TypeOf(val2)

[illia-li]

Right now, it's a single large commit. Ideally, it would be better to break it into smaller commits, but not in the way it was before, like "adding A" and then "optimizing part x of A." Instead, it should be more like "adding a" and then "adding b (not related to a)". For example, in this PR (#256), each commit focuses on adding or fixing one specific thing. If a commit is fixing something, it's from the master branch or was added before that PR, not something introduced in the same PR. Does that make sense?

In general, it makes sense.
But this PR does not change the current code at all, it is adding test suite.
This can be done in different ways, just tell me how.

resolve conversation v1...resolve conversation vn was needed so that the github would not lose conversations.

[dkropachev]

Right now, it's a single large commit. Ideally, it would be better to break it into smaller commits, but not in the way it was before, like "adding A" and then "optimizing part x of A." Instead, it should be more like "adding a" and then "adding b (not related to a)". For example, in this PR (#256), each commit focuses on adding or fixing one specific thing. If a commit is fixing something, it's from the master branch or was added before that PR, not something introduced in the same PR. Does that make sense?

In general, it makes sense. But this PR does not change the current code at all, it is adding test suite. This can be done in different ways, just tell me how.

resolve conversation v1...resolve conversation vn was needed so that the github would not lose conversations.

I also agree that there is no reason to have it splitted into commits, even though it has 15 files, all of them a there to do exact one thing, which is in line with the commit message.

[dkropachev]

@illia-li , please don't resolve conversations, answer in the thread instead.

[illia-li]

We will continue working on the corrupt tests here?

[dkropachev]

We will continue working on the corrupt tests here?

No, let's merge it in and continue on another PR.

[illia-li]

Let`s merge it:)

[dkropachev]

@sylwiaszunejko , can you pleae take another look, i am ok with this PR.

[sylwiaszunejko]

@illia-li Thanks for your work!

[dkropachev]

@illia-li Thanks you, sorry for being so picky