Hi gophers!
I would like to announce v1.1 of go-mutesting
https://github.com/zimmski/go-mutesting/releases/tag/v1.1
Changes from 1.0 to 1.1
- Mutator for the comparison operators “<”, “<=”, “>” and “>=” to catch
off-by-one problems
- Complete blacklist of reserved and built-in keywords tha
I fully agree with Aaron. Both are fine additions but they should be opt-in
instead of opt-out. "We" (and myself) have Vet in the linting stage of all
of our projects. We do not want to run a static analysis in the test stage.
Also, until the dependency issue is fixed for all possible scenarios
Hi gophers!
I am trying to integrate -msan for testing into
https://github.com/go-clang/bootstrap using Go 1.7.1 and LLVM 3.9.0 inside
an Ubuntu Trusty 64bit VM. The Kernel is 3.13.0.
I am executing a test using the following command:
CC=clang CGO_LDFLAGS="-L`llvm-config --libdir` -fsanitize=m
Hi gophers!
I am wondering why we have a "declared and not used" compile error for
variables [https://play.golang.org/p/KLzHVO5L7q] but not for constants
[https://play.golang.org/p/JG9dSa_VKg]? I am sure there is some rational
decision behind this that I have missed, but my Google-fu is just no
On Friday, September 9, 2016 at 1:51:49 PM UTC+2, Ian Lance Taylor wrote:
> > I have the following questions concerning the usage of the -msan flag:
> > a.) Are these the preferred arguments to use the -msan flag?
>
> Looks OK to me.
>
I am wondering if they are really needed, and if yes, why
On Monday, September 12, 2016 at 3:41:35 PM UTC+2, adon...@google.com wrote:
>
> On Monday, 12 September 2016 08:57:15 UTC-4, Markus Zimmermann wrote:
>>
>> Hi gophers!
>>
>> I am wondering why we have a "declared and not used" compile error for
>> v
On Monday, September 12, 2016 at 3:21:50 PM UTC+2, Sjon Kosse wrote:
>
> Hello,
>
> Const values can be accesed still by reflection in a reasonable manner.
> This question has come by quite a few times before on the mailing list,
> better explanations should be easy to find.
>
I do not think tha
On Tuesday, September 13, 2016 at 3:50:12 PM UTC+2, Alan Donovan wrote:
>
> On 13 September 2016 at 08:22, Markus Zimmermann > wrote:
>
>> On Monday, September 12, 2016 at 3:41:35 PM UTC+2, adon...@google.com
>> wrote:
>>>
>>> unused constants and type
On Wednesday, September 14, 2016 at 3:47:29 PM UTC+2, Chris Hines wrote:
>
> On Monday, September 12, 2016 at 8:57:15 AM UTC-4, Markus Zimmermann wrote:
>>
>> Hi gophers!
>>
>> I am wondering why we have a "declared and not used" compile error for
On Wednesday, September 14, 2016 at 3:37:10 PM UTC+2, Alan Donovan wrote:
>
> On 14 September 2016 at 09:32, Markus Zimmermann > wrote:
>>
>> Do you think this might be worth bringing up in golang-dev?
>>
>
> No. We can't make this change to the language
This looks pretty neat. We did something similar for
https://github.com/go-clang/ The generator is here
https://github.com/go-clang/gen and a resulting binding is here
https://github.com/go-clang/v3.7 Maybe we can find some inspiration from
each others projects? It would be also interesting to
your changes :-) Contact me if you need any
ideas/opinions.
I mentioned some concerns about cgogen here
https://github.com/go-clang/design/issues/9 if you are interested. I can
also over my help in setting up TravisCI and Coveralls, and making the
whole repository more "go-ish".
On Tue
Isn't this like saying a whole country is bad because of its
president/leader? A whole community cannot be bad because of what one
person did, nor can a whole company because of its CEO. golang-nuts/-dev
would not be closed if one Google person behaves bad. We are a community of
our own, we are
Hi gophers!
A while ago I took over maintainership of https://github.com/sergi/go-diff
which is a package to diff, match and patch text. The original code is a
port of Neil Fraser's google-diff-match-patch by Sergi Mansilla. I am
almost finished with what I wanted to do when I started this, whi
Hi gophers!
I would like to announce v1.0 of go-mutesting
https://github.com/zimmski/go-mutesting
The following has changed since the last release:
- Added a build-in exec command so only the go-mutation binary is needed
for mutation testing in the most common use-case.
- Added a mutator for "c
I also would like to see some examples. Also, please make the whole project
go-getable.
Looking forward to see where this project is going, exciting! Can you link
to the papers where you demonstrate that you outperform picosat and minisat?
On Saturday, July 23, 2016 at 11:33:31 PM UTC+2, Scott
Given the following code https://play.golang.org/p/1_Q9SFIPjr one can see
that stdout of Go and cgo are piped to two different descriptors.
a.) Is it possible to redirect stderr/stdout of cgo calls directly to
os.Stderr/os.Stdout? Am I overlooking some argument or options of cgo so
that is done
I feared that there would be no pure Go solution. Anyway, I used fdopen
variant the code is here
https://github.com/zimmski/osutil/blob/master/capture.go#L51 if anyone
every stumbles over this thread.
Thanks for the help.
On Monday, July 25, 2016 at 1:00:46 PM UTC+2, Uli Kunitz wrote:
>
> Your
You are right Sebastien, I fixed that. Thanks!
On Thursday, August 4, 2016 at 6:58:06 PM UTC+2, Sebastien Binet wrote:
>
>
>
> On Thu, Aug 4, 2016 at 1:07 PM, Markus Zimmermann > wrote:
>
>> I feared that there would be no pure Go solution. Anyway, I used fdopen
>
of
> stdin/stdout as FILE*.
>
>
> On Thursday, August 4, 2016 at 8:07:40 PM UTC+9, Markus Zimmermann wrote:
>>
>> I feared that there would be no pure Go solution. Anyway, I used fdopen
>> variant the code is here
>> https://github.com/zimmski/osutil/blob/master/c
gt;
>
> ★
>
>
>
>
>
>
>
> ★ - ps wins
>
> ☆ - g768l w
We switched from SQLite to PostgreSQL as our "in memory" database. We use
an SQL database so we do not have to mock DB calls and maintain an
interface. If that is something that is interesting i could trigger a blog
post about what we did and why?
On Tuesday, July 27, 2021 at 10:21:23 AM UTC+2
Hi Gophers!
We were unhappy with the common unit test styles and we think we found a
style that has clear advantages. An in-depth comparison can be found here
https://symflower.com/en/company/blog/2022/better-table-driven-testing.
We also added support for maintaining such tests in our VS Code
are coming. Takes some time because we need to
alternate between product work.
On Friday, 25 February 2022 at 19:48:19 UTC+1 Markus Zimmermann wrote:
> Hi Gophers!
>
> We were unhappy with the common unit test styles and we think we found a
> style that has clear advantages. An in-d
[image: with-go-test-with-test-runner.png]
We implemented a basic test impact analysis that identifies and then
executes affected tests for a change, e.g. for a range of commits. Our
benchmark for the repositories we looked at shows an average 29% reduction
in test execution time. I am very mu
25 matches
Mail list logo
