Breakpoint is not enabled on reloaded file

[ko1]

Now reloaded file removes the breakpoint.

# a. rb

load './b.rb'
foo

load './b.rb'
foo

# b.rb
def foo
  p 1
end

[master]$ ../../exe/rdbg a.rb
[1, 6] in a.rb
     1|
=>   2| load './b.rb'
     3| foo
     4|
     5| load './b.rb'
     6| foo
=>#0    <main> at a.rb:2
(rdbg) b b.rb:3    # break command
#0  BP - Line (pending)  /mnt/c/ko1/src/rb/ruby-debug/tmp/v44/b.rb:3
(rdbg) c    # continue command
DEBUGGER:  BP - Line  /mnt/c/ko1/src/rb/ruby-debug/tmp/v44/b.rb:3 (call) is activated.
[1, 4] in /mnt/c/ko1/src/rb/ruby-debug/tmp/v44/b.rb
     1|
     2| def foo
=>   3|   p 1
     4| end
=>#0    Object#foo at /mnt/c/ko1/src/rb/ruby-debug/tmp/v44/b.rb:3
  #1    <main> at a.rb:3

Stop by #0  BP - Line  /mnt/c/ko1/src/rb/ruby-debug/tmp/v44/b.rb:3 (call)
(rdbg) c    # continue command
1                                                                                                                      <== DON'T STOP AFTER RELOADED
1

ruby/vscode-rdbg#44

[ko1]

Questions:

1. Should we remain the breakpoints? The file can be modified when the next loading and the lines can be strange.
2. Should we keep the BP pending information?

[st0012]

For 1, I think we should keep the breakpoints. Users specified the file and line number and that's what they have in mind through out the debugging session. Even if the location ended up being in a funny state, it's still easy for them to figure that out. On the contrary, losing a breakpoint after file reload is not what I'd expect as a user and it limits what I can do in a debugging session.

For 2, I haven't felt it helpful but I'm ok if we keep it for now.

[ko1]

Let's try to leave on same lines even if the file was changed.