My Nim Development Weekly Report (4/2)

[ringabout]

## Progress

### chores

[fixes changelog](https://github.com/nim-lang/Nim/pull/21590)

[fixes booting warnings](https://github.com/nim-lang/Nim/pull/21583)

### create type bound operations for calls in the method dispatcher for ORC

[fixes #21592; create type bound operations for calls in the method dispatcher 
for ORC](https://github.com/nim-lang/Nim/pull/21594)
    
    
    import std/options
    
    type Event* = object
      code*: string
    
    type App* = ref object of RootObj
      id*: string
    
    method process*(self: App): Option[Event] {.base.} =
      raise Exception.new_exception("not impl")
    
    
    Run

It now works.

### Write an RFC for adding compiler support for object construction shorthand

[compiler support for object construction 
shorthand](https://github.com/nim-lang/RFCs/issues/517)

### [PR] disable BareExcept warning in panics:on mode

[disable BareExcept warning in panics:on 
mode](https://github.com/nim-lang/Nim/pull/21605)
    
    
    try:
      raise newException(CatchableError, "catched")
    except:
      discard
    
    
    Run

With `--panics:on`, the compiler does not give `BareExcept` warnings.

### [PR] warn on overloaded =copy with refc

[fixes #20846; fixes #21427; warn on overloaded =copy with 
refc](https://github.com/nim-lang/Nim/pull/21606)

### [PR] implement =dup hook eliminating wasMoved and =copy pairs

[implement =dup hook eliminating wasMoved and =copy 
pairs](https://github.com/nim-lang/Nim/pull/21586)
    
    
    proc `=dup`(s: ref): ref =
      dest[] = src
      if src != nil: nimIncRef src
    
    
    Run

The `=dup` hook is for optimization. The compiler sometimes generates 
`=wasMoved(x); =copy(x, y)`. But `=wasMoved` is unnecessary in this case since 
it is going to be rewritten for sure. It should be replaced by `x = =dup(y)` 
instead.

## Weekly collection

<https://forum.nim-lang.org/t/9908> (2/19)

<https://forum.nim-lang.org/t/9940> (2/26)

<https://forum.nim-lang.org/t/9970> (3/5)

<https://forum.nim-lang.org/t/9989> (3/12)

<https://forum.nim-lang.org/t/10024> (3/19)

<https://forum.nim-lang.org/t/10040> (3/26)

## Participating in contributions

Following [The Roadmap 2023 for community building 
](https://github.com/nim-lang/RFCs/issues/513), you could join us in [the 
matrix 
space](https://matrix.to/#/!ZmWXggMgfkKpcLbQkB:matrix.org?via=matrix.org) where 
we discuss how to build a community. We appreciate doable suggestions and 
helps, such as improving the workflow, implementing the roadmap, suggesting 
doable tasks, reviewing code from contributors. United we stand. We shall work 
together to make the community thrive.

## Sponsorship

Many thanks to @Yepoleb, @lenis0012, @pietroppeter, @Clonkk, @mode80, @Phil, 
@CxPlanner, @shirleyquirk, @elcritch, @geotre, @thinkwelltwd, @xrfez, 
@enthus1ast, @piertoni, @Dnanilem, @gemath for [sponsoring me on 
GitHub](https://github.com/sponsors/planety).